Closed crysxd closed 3 years ago
Are you using auto resolution? If not, when you run the command a second time with --debug, the version code will have been used up from the time it succeeded without --debug. You'll have to bump the version code between builds.
I found a stray resolutionStrategy.set(ResolutionStrategy.IGNORE)
🙈Thanks for the hint!
Describe the bug
I had an issue with my version code causing a old version code which already was uploaded to Google Play to be used again. I know from making a similar mistake some time ago that this caused the build to fail and a error response from the Google Play API to be shown in the logs. Now (versions below) this does not cause the build to fail for me and the 403 error is only shown in builds with
--debug
set.How To Reproduce
Versions
(Same issue with AGP+gradle 7 and the matching 3.5.0-agp7)
Tasks executed
publishReleaseBundle
Expected behavior
Build fails after 403
Additional context (if a crash, provide stack trace)
This build did not upload anything (because same version code)
Same tag with
--debug
I replaced sensitive data with (redacted), please note the Bearer token was logged once