Google Play发布失败,并显示“请求路径中的曲目名称,并且请求正文必须匹配". [英] Google Play publishing fails with "Track names in request path and request body must match"

查看:76
本文介绍了Google Play发布失败,并显示“请求路径中的曲目名称,并且请求正文必须匹配".的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

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

I'm using Codemagic to build and publish apks to Google Play's internal track, on March 10 it was working fine, but today I got this:

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中存在内部错误.现在已经解决了,一切都按预期进行了.

unfortunately there was an internal error in Codemagic. It has been resolved for now and everything works as expected.

这篇关于Google Play发布失败,并显示“请求路径中的曲目名称,并且请求正文必须匹配".的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆