Skip to content

Downgrading priority not being respected. #1076

@mattbusuu

Description

@mattbusuu

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugIndicates an unexpected problem or unintended behaviordontclosePrevents the stale bot from closing this issue/pr

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions