英文:
Android : How to add QA build variant into the internal testing track to test the Android's in-app update API?
问题
我已经按照官方文档提供的步骤将Android的应用内更新API集成到我的Android应用程序中：Google官方文档和Google官方文档，现在我想使用我的QA构建变体测试应用内更新流程。
当我尝试将Android QA构建变体上传到Google Play控制台的内部应用共享上传页面（内部应用共享）时，我遇到了错误。
我不确定，但我认为这可能是因为应用程序ID（即包名）不同，因为我在原始应用程序ID后附加了“.qa”后缀（applicationIdSuffix '.qa'）。
是否有办法在保持应用程序ID后缀的情况下将QA构建上传到Google Play控制台的测试轨道？
此外，官方文档中提到：“要设置更新的优先级，请在Google Play开发者API的Edits.tracks.releases下使用inAppUpdatePriority字段。优先级只能在推出新版本时设置，以后不能更改。”这是否意味着我将无法测试QA构建环境中的更新优先级和即时更新？
是否有办法可以测试上述所有内容？请帮助...！
英文:
I have implemented the Android's in-app update API into my android application by following the steps given by Official documentation: Google Official Document and Google Official Document and now I want to test the in-app update flow with my QA build variant.
I am getting an error while trying to upload the android QA build variant into the internal app sharing upload page (internal app sharing) i.e. internal testing track of Google play console.
I am not sure but I think this happens because of different application id (i.e. package name) as I append .qa suffix to original application id. (applicationIdSuffix '.qa')
Is there any way to upload the QA build into the testing track of Google play console by keeping suffix to application id.
Also, the official document says that "To set the priority for an update, use inAppUpdatePriority field under Edits.tracks.releases in the Google Play Developer API. Priority can only be set when rolling out a new release, and cannot be changed later." Does that mean I won't be able to test the update priority with QA build environment and thus the immediate update?
Is there any way where I can test all the above things? Please help...!
专注分享java语言的经验与见解，让所有开发者获益！
评论