2

I am implementing In-app Update API. Both Flexible and Immediate update flow works fine based on the update priority.

But for some reason AppUpdateInfo returns updatePriority of previouls release.

For Example,

Build number and its priority set through Google Play Developer 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.

Mohit Charadva
  • 2,555
  • 1
  • 22
  • 30
  • It will be good if you also share your code for reference. – Keyur Shrimali May 12 '21 at 15:50
  • Could you please look at [this question](https://stackoverflow.com/questions/67970359/can-we-set-update-priority-for-internal-app-sharingtesting-in-app-updates)? This is my question as well and seems you are able to set the priority. – msc87 Jun 29 '21 at 13:48
  • 1
    @mohit Could you please share the steps to set the priority? – Ravi Jul 15 '21 at 09:17
  • is it because the app information is cached? or is it because it is internal test? – Raii Jun 02 '22 at 16:40

1 Answers1

-1

To determine priority, Google Play uses an integer value between 0 and 5, with 0 being the default and 5 being the highest priority. To set the priority for an update, use the inAppUpdatePriority field under Edits.tracks.releases in the Google Play Developer API. 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.

Arda Kazancı
  • 8,341
  • 4
  • 28
  • 50