Android developer "Upload new APK to Production 99% complete" and stuck Android developer "Upload new APK to Production 99% complete" and stuck android android

Android developer "Upload new APK to Production 99% complete" and stuck


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.