What?
When running reusable android release action there are pre-requisites that both an android build has previously submitted to the play store and that the current build has a version number that is an increment.
It would be good to manually confirm this in advance when running the build action and providing user feedback if action required
Why?
The deployment action will fail with messages that aren't always very obvious (and will take a reasonable amount of time building before getting to that stage). E.g. if version number not incremented error output:
You cannot rollout this release because it does not allow any existing users to upgrade to the newly added APKs.
How?
Likely adding a step to the release action to be called before full build (or passing as a parameter to the build step to check) that communicates with the google play store api to check for existing releases and their version numbers.
What? When running reusable android release action there are pre-requisites that both an android build has previously submitted to the play store and that the current build has a version number that is an increment.
It would be good to manually confirm this in advance when running the build action and providing user feedback if action required
Why? The deployment action will fail with messages that aren't always very obvious (and will take a reasonable amount of time building before getting to that stage). E.g. if version number not incremented error output:
How? Likely adding a step to the release action to be called before full build (or passing as a parameter to the build step to check) that communicates with the google play store api to check for existing releases and their version numbers.
Other details Android publisher api: https://developers.google.com/android-publisher/tracks