After making changes to my project I have uploaded it to Google Play. Some time after I've tried to update it (Google Play has been already refresh application info and I saw new version number) but I've got an error - "Error retrieving data from server RPC:S-5:AEC-0...". Same report appears on my other devices (5pcs) and users began to mail me with same problem.
Searching gives me this support report. After minutes of googling I found solution - reconnect Google account and it works for me. But I have 40k users - what can I do to help them all? I've implemented new fancy features in game and now they available only for new users.
So, question is - does anybody faced already with such problem? What have you done to solve this?
Related
I've recently uploaded an update of an app and I am unable to install it. It only shows this dialog and no further info is provided. Contacting Google Support proved useless, so you're my only hope..
Sorry it's in Czech. It roughly translates as "Application MOU EDU cannot be installed. Try again and if the problem persists, read about common ways of fixing it."
Suddenly from 3 days, I am not able to use Google Internal App sharing. Loading App sharing page fails with error "unexpected error". Is there anyone else who faced this issue? and have some workaround?
Note:
I am aware that I should raise this issue in Google support, but they are taking too much time to respond. Meanwhile, I am just searching for workarounds or possible reasons for it.
I have tried all possible solutions which are already there on the Web, like incognito mode, clearing cache, etc.
In my network those who already have play store accounts are also getting the same issue.
The API gateway still seems to work. I was able to upload a test apk/aab via fastlane.
It's an easy setup. Then use the upload_to_play_store_internal_app_sharing command to upload the apk/aab
I set up a basic Google Firebase integration for my Android mobile app, it worked fine for a couple of days but then suddenly the Google Analytics console started showing the data just for the most recent 3 days. It's been a consistent behavior for the past week - everyday when I check the data I only see the most recent 3 days. And the older data that was present the day before is missing.
This is my second mobile app that I integrated with Google Firebase and the first one doesn't seem to have this issue.
I tried searching for similar issues on the web but nothing relevant comes up. I also went through all the possible settings in Analytics console, but nothing seems suspicious.
What can be the cause of this?
UPD: I found this thread in the meantime https://support.google.com/analytics/thread/83254216?hl=en Maybe there'll be some resolution there
I had updated my apk file and build a new version (upgrading the versionCode and versionName).
The files was successfully uploaded on the apk 2 days back, but still it is not updated :(
Can some one pls help me.
Its still showing "Processing update" as status on the console.
I tried un-publishing the app and re-publishing the same, it made thing even worse.
Now M unable to search my application.
Tried contacting the google guys, but still no progress.
Please help
Found a similar qstn here
My android app is not being updated on the Google Play Store
For a new app you need to have patience. It may take anything from 2 days to a week. There will be reviews and automated policy checks etc happening after which it will be available on store.
By republishing you just restarted the whole process.
Usual process may take maximum one week. Here only you can do is wait till they respond.
The chances are there the app may be rejected for the update, due to some technical reason. Keep on checking the status change. Also create a query to Google.
I have attempted to upload an app via the Google Play Developer Console for the last two days, but the apk uploads until "99% complete" in firefox or until "processing" in chrome and the is stuck.
This is not my first app. I have uploaded and published two others without incident.
I have attempted the upload with following with all the same result:
*Firefox 28.0 (Ubuntu 13.10)
*Firefox 28.0 Incognito (Ubuntu 13.10)
*Chromium Version 33.0.1750.152 (Ubuntu 13.10)
*Chromium Version 33.0.1750.152 (Ubuntu 13.10) Incognito
*Chrome mobile 33.0.1750.166 on Galaxy Nexus Android 4.2.1 phone
*Chrome (Windows 8)
Logs start out fine:
POST https://play.google.com/apps/publish/upload [HTTP/1.1 200 OK 537ms] POST https://clients2.google.com/uploadstats [HTTP/1.1 200 OK 1402ms] POST https://clients2.google.com/uploadstats [HTTP/1.1 200 OK 1457ms] POST https://play.google.com/apps/publish/upload
then it hits 99% complete and these errors start posting:
POST https://play.google.com/apps/publish/upload [HTTP/1.1 503 Service Unavailable 3816ms] POST https://play.google.com/apps/publish/upload [HTTP/1.1 503 Service Unavailable 739ms] POST https://play.google.com/apps/publish/upload [HTTP/1.1 503 Service Unavailable 668ms] POST https://play.google.com/apps/publish/upload
I also tried advancing the version in the AndroidManifest.xml.
As a test I added the apk in question to the Amazon Appstore. No difficulties. The apk uploaded seamlessly. Google Play Store issue?
Also tried adding a new application in the developer console and then uploading the apk.
Also tried starting from scratch and rebuilding the app in Eclipse and then attempted to upload the new apk. No luck
I have been emailing with Google Help. 8 days ago they asked for the apk in question and HAR file generated when the upload gets stuck. I sent both. They replied they were looking into the issue. A few days later this question came alive with others experiencing the same issues! I emailed again that I was still encountering issues.
Then on March 19th they responded and asked for:
A screenshot of the error message.
The APK you're attempting to upload
The browser versions you were able to test with and OS type that you are using.
Information from the browser's error console or http logs.
What steps did you take to reproduce this issue?
Any other suggestions?
There is a bug in Android that affects every version of it. A developer found out about it yesterday. By malforming an apk file you can corrupt system memory and systems freezes completely. He then uploaded this malformed apk to Goople Play from different countries causing Google Play Developer Console to freeze all over the world! It was fixed for about an hour but then the developer reuploaded the apk and Google Play is down again. I think it will be fixed soon, but anyway it can lead to huge financial damages to many companies around the world.
http://ibrahimbalic.com/2014/android-os-memory-corruption-bug/
So the answer is we just have to wait...
It's a temporary problem, common to many users, due to google developer console website problem.
After tring many times at different hours you will finally upload your app.
This is my experience.
Here the link to the problem report: https://code.google.com/p/android/issues/detail?id=67226
Here the link to report the problem directly to Google requesting support: https://support.google.com/googleplay/android-developer/contact/publishing?extra.IssueType=submitting
It was a problem on Google's end, and they were aware of it; there was a message on their support site (which now appears to have been taken down) and in the Developer Console alerts:
Errors uploading to the Google Play Developer Console:
We're currently aware of an issue impacting some developers attempting
to upload APKs or Images to the Google Play Developer Console. We're
working hard on a fix, and will provide an update once the issue is
resolved.
Google states it now appears to be fixed:
UPDATE - 2014.03.17 4:00PM PT:
This issue is now resolved. Please contact us if you see any issues
uploading APKs or Images.
I have been able to publish APKs and also received numerous app updates since this message was posted, so it does appear that this specific problem appears to be resolved now.
My specific issue was identified by the Google Support team:
Our specialists have found that the APK was getting stuck during the
step where we verify the icon and the certificates.
Comparing the aapt dump to your app's manifest, there are some
inconsistencies with the icon location. You would want to start
troubleshooting there. If after fixing the icon you still encounter
upload issues, double check your certificates and your signing
procedure.
The issue was entirely mine as a new and inexperienced developer.
Upon replacing the icon and redoing the key in Eclipse, the .apk in question uploaded without incident and is now published.
The Google Team also made the following suggestion for those searching for help:
For more information on running aapt, please see the “Testing the features required by your application” section of the following article: http://developer.android.com/guide/topics/manifest/uses-feature-element.html.