What does the "An unexpected error occurred. Please try again later. (-32600)" mean? Today I tried to upload a new version/APK and I received this error. It offered me to save it as a draft. Now I can't Unpublish it, Delete version, Deactive version or anything else. I'm stuck with this error. I tried to Deactivate last published version. to Unpublish the whole application, to delete "Draft in Beta" versions. But whatever I do I get that error. I even tried to logout and login again. And tried different browser. Nothing helps. Anybody got an idea what could be wrong and how to solve this?
Same error here.
I contacted Google Support:
"We had an issue with our most recent update for the Developer Console and have rolled back the changes. You should be able to manage APKs and publish your app normally in the next few hours. If you still receive an error message by the end of today, please let me know and I'll be happy to investigate further."
I found a work around. Go to the APK section in your dashboard and click unpublish from there in the top menu. It gives an alert that it may take a few hours to be removed from the play store. Worked for me :)
Related
This is my first time attempting to publish a mobile app to the Google Play store. I paid for the ability to use the Google Play Console for publishing purposes. I have followed the tutorials, signed and built the release version (opted in for the android app bundle to try and make the process as easy as possible), and uploaded the .aab file in the correct place while creating a new release. During all this, there were no errors indicated in the console regarding the release. I filled out all the fields, clicked 'Save', and then clicked 'Review Release'. Upon clicking that last button, I received an error: 'An unexpected error has occurred. Please try again. (5A35450E)'.
I have searched numerous places looking for a solution to no avail.
I am using Google Chrome as my web browser.
Has anyone else ran into this issue? If you did, how did you solve it?
It may Sound Dumb but I managed to fix it for myself and I don't know if this is solution but do as i say and i hope it will fix it, and it only worked this way
Get into the Draft Release page
Press on Review Release and wait for the error
Disable Anti-Virus (In My case is Avast Free)
Return to Chrome and you will get SSL Error.
Press F5, and you should see the new page
Press roll-out release
Note: If u disable Avast before getting the error, it will not work.
I figured out what my problem was.
Since I had selected US as a deployment region, it is required to have a privacy policy. I am not collecting any data from people, so I didn't create a privacy policy initially since the console stated I didn't need one. Once I added a privacy policy, it allowed me to continue with the release.
I recently published on android app on the playstore and I had no problem or warning.
Although, people can't download the app because I had activated the "pre register feature"(without knowing what it was ....) and thinking It had no impact.
It looks easy to deactivate the feature on the play console developer dashboard, but every time I try to deactivate it, I am getting this error message :
"An unexpected error occurred. Please try again later. (668269003)"
I have successfully checked the "inactive" box all the countries but one hoping it will solve the issue but for now, I still can't download my own app.
Should I just wait and try again ? Any ideas ?
An other idea I had was to change the "Launch deadline: Nov 4, 2019" in order to make it shorter so that It would solve my issue, but I have no idea how to change that deadline date.... (I don't even remember seing that date when I uploaded my package on the store)
thanks for any help.
I received the same error #668269003 when trying to disable pre-registration for an app that I was trying to publish to the Open Beta track. Before disabling pre-registration, the console indicated that the Open Beta should be available and should override pre-registration for the pre-registered countries when using the SYNC WITH PRODUCTION setting.
To work around this, I did the same as you and disabled all but one country (not my country, or the countries I'm actually interested in for now) in pre-registration, which does appear to save without the error.
From there, I went into the release track for the release I'm interested in (in my case, Open Beta), and selected CUSTOMIZE AVAILABILITY and manually ticked the countries that used to be enrolled in pre-registration.
After saving and letting the Google server pixies do their "processing update" shenanigans, the app finally showed up with the option to install rather than pre-register.
I've opened a request with Google, if in the unlikely event they get back to me for some reason I'll update this reply.
I assume that these steps should also work for the production track, but I'm not yet in a position to test there.
Note that the launch deadline is the date you enable pre-registration in a given country, plus 90 days. I don't believe it is editable.
Similar to #repentspinner, with the new google console I was able to enable pre-registration for a small country I didn't care to release to, then I was able to disable it for the actual country I was targetting. This triggered a review process which took <24 hrs. Once past review the app now shows 'install' as expected.
My app is available on the Play Store and one of my users reported that it crashes on his phone but he is not able to send me the logs since there is no report dialog.
What could be the source of this issue and how to fix it ?
I would suggest you send another build with crashlytics and criticism in place and try to replicate the crash. Also go to your dashboard of play store and check for crash logs.
Today I added my first application to play google stores. Send your application went smoothly. The application was in store. But as I want to download this application pops up an alert: Authentication is required. Sign in with your Google Account. I might also add that I am logged into your Google account, and checking whether the application runs on several other phones. But unfortunately, the situation repeated itself. Very Please help.
I had the same problem and how to fix it is very simple just go to your apps description and update it with anything I just added one word clicked update and an hour later worked perfectly
I cant comment as I am a new user.
But it seems its an issue with the Google Play, as every one is facing the same issue.
I got 7 apps uploaded yesterday and none of them are working. I have retried to upload again today, and waiting to see the outcome.
Let me know if your apps are working fine now or if any updates on this.
I developed and published an App to Google Play and it was working fine until yesterday. App works as it should but when the users want to open the Achievements and Leaderboard in Google Play they get an error: "Unfortunately, Google Play services has stopped"
I know that the App is able to login into GP because I created some messages that update after login
public void onSignInSucceeded()
{
if(getApiClient().isConnected())
{
loading.setText("Please wait while we load\n the Achievements panel, thank you...");
...
}
....
}
but the App cannot display the Achievements/Leaderboard anymore as it ones did.
I am not sure if anything changed with Google Play or Play Games but it just stopped working. Did't make any changes in the code nor uploaded a new package to Google Dashboard. It just simply stopped working... any thoughts?
thank you,
Dan
Update: the Stack trace error message is:
java.lang.NumberFormatException: Invalid long: "" at java.lang.long.invalidLong(Long.java:124) at java.lang.Long.parseLong(Long.java:345) at com.google.android.gms.games.ui.client.a.a(SourceFile:498) at com.google.android.gms.games.ui.client.a.b(SourceFile:344) at com.google.android.gms.commom.internal.z.a(SourceFile:188)
Google Play Services has just been updated! This fixed the error for us. So hopefully this will work for everyone else :)
Just download the latest version and it should work.
Sorry for creating this as an answer, but apparently I can't comment as a new user. And we have no clue how to solve this error.
We have had the same error since yesterday. Everything worked perfectly before that, and players can still acquire achievements, but showing the Achievements UI crashes the game with a message: Google Play-services has crashed.
We tried downloading our 1.0 version from Play Store, and the same thing happened in that version. In other words: This can't be something we changed in our code. We have tried practically everything we can think of.
the API call that seems to trigger this is:
AndroidNativeBridge.GetInstance().startActivityForResult(
Games.Achievements.getAchievementsIntent(mHelper
.getGoogleApiClient()), ACHIEVEMENTS_REQUEST);
Sorry again for posting as an answer, but this is the first related error we have found online.