-
Notifications
You must be signed in to change notification settings - Fork 26
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
Add a validation check with app/playstore prior to publishing a release #656
Comments
Looks like an option for this was added recently to |
and maybe |
This page might be useful to check manually as part of our release process https://developer.android.com/distribute/play-policies |
following the mixup with #659 , I tried running the fastlane This is the output from fastlane on my machine, after building the apk locally using
|
Our current process to publish a new release looks like:
dev
tomaster
master
via our release scriptAt this point, we've waited several hours, and our release hasn't gone through. In some cases, like today, one store accepts the release, but not the other one. To keep release numbers in sync, we now have to figure out what the problem is, fix in
dev
and restart the whole process.It would help to have a way to validate that a release will be accepted by the stores before we send it "officially", which would save hours. I suspect there might be a way to do this with
fastlane
, but haven't found the solution yet.The text was updated successfully, but these errors were encountered: