简体   繁体   English

应用内更新 API 从以前的版本返回 inAppUpdatePriority

[英]In-app Updates API returns inAppUpdatePriority from previous version

I am implementing In-app Update API .我正在实施应用内更新 API Both Flexible and Immediate update flow works fine based on the update priority .灵活和即时更新流程都可以根据更新优先级正常工作。

But for some reason AppUpdateInfo returns updatePriority of previouls release.但由于某种原因, AppUpdateInfo返回上一个版本的updatePriority

For Example,例如,

Build number and its priority set through Google Play Developer API.通过 Google Play 开发者 API 设置内部版本号及其优先级。

   Version code     Priority
1. 109 (Installed)      0
2. 110                  3
3. 111                  5
4. 112                  2

When I check for the update inside the app update priority is of the previous release.当我检查应用程序内的更新时,更新优先级是以前的版本。

   Update check     Priority
1. 110                  0
2. 111                  3
3. 112                  5

I don't know what I am doing wrong here because everything is working fine only the update priority that I am getting from In-app Update API has an issue.我不知道我在这里做错了什么,因为一切正常,只有我从应用内更新 API 获得的更新优先级有问题。

To determine priority, Google Play uses an integer value between 0 and 5 , with 0 being the default and 5 being the highest priority.为了确定优先级,Google Play 使用介于05之间的 integer 值,其中0是默认值, 5是最高优先级。 To set the priority for an update, use the inAppUpdatePriority field under Edits.tracks.releases in the Google Play Developer API.要设置更新的优先级,请使用 Google Play Developer API 中 Edits.tracks.releases 下的 inAppUpdatePriority 字段。 All newly-added versions in the release are considered to be the same priority as the release.发行版中所有新增的版本都被认为与发行版具有相同的优先级。 Priority can only be set when rolling out a new release and cannot be changed later.优先级只能在推出新版本时设置,以后不能更改。

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM