-
Notifications
You must be signed in to change notification settings - Fork 5.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Promoting non-latest alpha track version to production fails on Google Play Store #18497
Comments
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Friendly reminder: contributions are always welcome! Check out CONTRIBUTING.md for more information on how to help with This issue will be auto-closed if there is no reply within 1 month. |
I do not see an improvement. |
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Friendly reminder: contributions are always welcome! Check out CONTRIBUTING.md for more information on how to help with This issue will be auto-closed if there is no reply within 1 month. |
I don't see how it will magically get fixed. But, no, no change. Please someone give this bug some love. 🙏 |
This is still a problem |
I see the same when promoting from internal to alpha. Every time I upload a new build to internal, it makes the current as "replaced" in Google Play Console. |
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Friendly reminder: contributions are always welcome! Check out CONTRIBUTING.md for more information on how to help with This issue will be auto-closed if there is no reply within 1 month. |
This issue will be auto-closed because there hasn't been any activity for a few months. Feel free to open a new one if you still experience this problem 👍 |
I don't know how to elaborate further on this. |
Same here. But having the bot closing the issue when a fix hasn't been made doesn't seem like the right solution. 😞 |
New Issue Checklist
Issue Description
We have multiple builds in our Google Play Alpha track, and quite often we want to promote an earlier version in that track to production. When we specify the specific version to promote, and it's not the current one, we get this error:
Yet, when we run
google_play_track_version_codes
on the alpha track it returns the version code we specified.An example of our issue:
Command executed
Complete output when running fastlane, including the stack trace and command used
Environment
The text was updated successfully, but these errors were encountered: