android - Google Play发布失败,出现 “Track names in request path and request body must match”

标签 android google-play google-play-console google-play-developer-api codemagic

我正在使用Codemagic来构建apk并将其发布到Google Play的内部音轨,3月10日一切正常,但今天我明白了:

Publishing
35s



== Gathering artifacts ==

== Publishing artifacts ==

Publishing artifact app.apk
Publishing artifact app-prod-armeabi-v7a-release.apk
Publishing artifact app-prod-x86_64-release.apk
Publishing artifact app-prod-arm64-v8a-release.apk
Publishing artifact mapping.txt
Publishing app.apk, app-prod-armeabi-v7a-release.apk, app-prod-x86_64-release.apk, app-prod-arm64-v8a-release.apk to Google Play
Published app.apk to track internal
Published app-prod-armeabi-v7a-release.apk to track internal
Publishing proguard mapping mapping.txt to Google Play
Published app-prod-x86_64-release.apk to track internal
Publishing proguard mapping mapping.txt to Google Play
Published app-prod-arm64-v8a-release.apk to track internal
Publishing proguard mapping mapping.txt to Google Play
Google Play responded with: Track names in request path and request body must match.

Build failed :|


Publishing failed :|
Google Play responded with: Track names in request path and request body must match.

最佳答案

不幸的是,Codemagic中存在内部错误。目前已解决,一切都按预期进行。

关于android - Google Play发布失败,出现 “Track names in request path and request body must match”,我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/60655450/

相关文章:

android - 无法在 android 中加载 libavcodec.so

java - 低于 24 的 android api 级别不支持

android - 可以调试从Play下载的Android应用?

android - 屏幕密度为 440 dpi 的设备与在 Google Play 上发布的应用不兼容

android - Google Play 内部测试轨道上应用的未知用户

android - 在 Android 中,如何强制 native 代码使用我的共享库版本,而不是系统的?

android - 总是创建延迟初始化的对象

android - android中cardview中带有三个点的小部件的名称是什么?

android - 在市场上上传 apk 时,apk 必须使用与以前版本相同的证书进行签名

android - Google Play : Can't RELEASE TO PRODUCTION because "a draft release in production already", 怎么办?