Cannot View Google Play Console Release Warning Messages
Asked Answered
T

3

9

When I try to confirm a rollout to internal testers in the Google Play Console for an Android app, I'm getting the following...

Check these warnings before starting the rollout of this release. Addressing the warnings on this page will ensure your existing users are able to upgrade to the latest version of your app.

If I try to click on the "VIEW WARNING MESSAGES" button below this message, I get

An unexpected error occurred. Please try again later.

enter image description here

How can I find out what the warning messages are so I can release my app to testing?

Tocantins answered 12/8, 2019 at 19:2 Comment(13)
We're also experiencing this. We had also uploaded an APK with version 1 (without rollout), then replaced the APK with one with version code 2. Not sure if that's relevant, but I noticed you had version code 2 also. We were able to see warnings before, but after mending the 64-bit requirement, we started getting this error.Voiced
Thank goodness. I thought it was just us. This is our first roll-out ever, and I was tearing my hair out.Esthonia
I have version 2 because I'd figure I'd try uploading the APK again to see if that helped but it did not.Tocantins
@Tocantins Did it help?Tolmach
We're having the same issue when trying to release, only the error-code is different: 2084869337Conglomerate
@Conglomerate The value is new every time, it is generatedTolmach
I figured... couldn't find anything by googling it. But what's the point of having unique, generated error codes if you cannot do anything to identify them? Because, they can surely not only be intended for internal Google analytics purposes?Conglomerate
The error code is different for every single attempt. Even I experience the same when I try to push to Google beta internal. Did anyone tried upload the apk to Alpha or Beta channels?Orts
I'm voting to close this question as off-topic because meta.#272665Hooten
When I posted this I thought maybe this was specific an issue with my APK but now it does appear to be an issue with the Google Play Store. I agree with the vote to close.Tocantins
Same issue here.Tham
Did anyone create a ticket to Google? If yes, please post the ticket number here for future tracking.Orts
For me, the issue of not being able to see the warnings cleared up this morning. I can see the warning now but that had nothing to do with the app not being able to be released. See Vadim Kotov answer below. Once I filled in all required sections, it let me release the app.Tocantins
T
1

In my case, I had to fill in all required sections in Store Presence in Google Play Console to be able to release the first version. I was confused by this "unexpected error" too.

enter image description here

Tolmach answered 14/8, 2019 at 9:40 Comment(1)
While not being able to view the warnings was an issue on the Google Play Console that seemed to clear up overnight, the real reason the app could not be released was that I had not filled in all required sections in the store listing. You have to make all the grey checkboxes green, then you can release. Would be nice to get a message that lets you know that.Tocantins
E
1

This apparently was an internal error within Google Play, that has been cleared up overnight.

Errors have started displaying correctly again.

It's good to know that when a Google error message says, "Try again later", unlike most platforms, they really mean it. Thanks, Google!

Esthonia answered 15/8, 2019 at 8:38 Comment(0)
O
0

Just tried with app bundle for one of my existing app. Deployed the app to internal beta program. I was successful in publishing. Guys. May be this is a problem with the apk format.

Orts answered 14/8, 2019 at 9:2 Comment(0)

© 2022 - 2024 — McMap. All rights reserved.