search

bitrise-steplib / steps-google-play-deploy

MIT License
54 stars 38 forks source link

Failed to validate edit, error: googleapi: Error 403: You cannot rollout this release because it does not allow any existing users to upgrade to the newly added APKs., forbidden #98

Closed KurasovAnton closed 3 years ago

KurasovAnton commented 4 years ago

Hi! I start getting this issue when trying to deploy APK to the google store using google-play-deploy step. I could deploy this build manually to the store. The google-play-deploy step works correctly a month ago. Does anyone have the same issue?

Thank you in advance.

bitce commented 4 years ago

Hi Kurasov!

Sounds like this might be an issue with the versionCode and/or versionName's value being less than the already deployed versions. Have you checked if that could be the case?

KurasovAnton commented 4 years ago

@bitce , thank you for such fast response. Yes, I've double-checked the build number and app version and it was greater than that one that was on google play console. Google console latest versions: App v2.5.0 build#4000102 Build that failed to deploy versions: App v2.6.0 build#4000110

Also, I've downloaded the APK from the bitrise and I could deploy it manually to store.

github-actions[bot] commented 3 years ago

Hello there, I'm a bot. On behalf of the community I thank you for opening this issue.

To help our human contributors focus on the most relevant reports, I check up on old issues to see if they're still relevant. This issue has had no activity for 90 days, so I marked it as stale.

The community would appreciate if you could check if the issue still persists. If it isn't, please close it. If the issue persists, and you'd like to remove the stale label, you simply need to leave a comment. Your comment can be as simple as "still important to me".

If no comment left within 21 days, this issue will be closed.

github-actions[bot] commented 3 years ago

I'll close this issue as it doesn't seem to be relevant anymore. We believe an old issue probably has a bunch of context that's no longer relevant, therefore, if the problem still persists, please open a new issue.