-
-
Notifications
You must be signed in to change notification settings - Fork 339
Open
Labels
bugIndicates an unexpected problem or unintended behaviorIndicates an unexpected problem or unintended behaviordontclosePrevents the stale bot from closing this issue/prPrevents the stale bot from closing this issue/pr
Description
Describe the bug
After releasing a second version of the app, the update priority is not being lowered.
E.g. Creating 2 releases, release A at priority 5, then release B at priority 1.
I am seeing priority 5 come back from the Google in App update API, despite setting priority back down to 1.
I have even tried removing it entirely but the result is the same. We are currently publishing to internal and then manually promoting the release from internal to production.
The gradle code is just as follows:
play {
updatePriority.set(0)
}
The task we are using to publish is:
- publishAppSigningReleaseBundle
Additional context (if a crash, provide stack trace)
We have managed publishing turned on
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
bugIndicates an unexpected problem or unintended behaviorIndicates an unexpected problem or unintended behaviordontclosePrevents the stale bot from closing this issue/prPrevents the stale bot from closing this issue/pr