Google play - can't upload apk any more..
Monkey Targets Forums/Android/Google play - can't upload apk any more..
| ||
Anyone else having issues uploading apk's to Google Play? Done this before with no problems, but when trying to do a minor update I get this error now: Upload failed You uploaded a debuggable APK. For security reasons you need to disable debugging before it can be published in Google Play. Learn more about debuggable APKs. I've signed and zipped the apk as per normal. Just wanted to see if anyone else has suddenly hit this issue? Googling around, seems like others are hitting this suddenly. Maybe something has changed/ is broken at Google's side? Can someone do me a favour and try uploading an apk (say as a beta or something) so see if they can replicate? Update: looks like other people (non-Monkey folk) are suddenly seeing this issue, too.. http://www.google.co.uk/?q=%22You+uploaded+a+debuggable+APK%22&safe=active#q=%22You+uploaded+a+debuggable+APK%22&safe=active |
| ||
Yeah. Google has changed something. They block now debuggable .apk. But they haven't posted anything about that. Maybe they will. To solve your problem, just add the following line to your AndroidManifest.xml file android:debuggable="false" |
| ||
Hey, that worked (I put the code you suggested into the <application bit of the AndroidManifest.xml file, btw), now all is good. I often get confused over the multiple versions of AndroidManifest.xml which float around in my monkey folder. For reference, the one I changed here was the one in the templates subfolder in the android folder of my build folder.. Seems Google have changed something after all. |
| ||
Same here, thanks for the solution! Mark could you please add that line to the manifest for one of your next releases? |
| ||
Seems like a mistake by Google really, their docs say it's un-debuggable by default! |
| ||
I don't think so. I think, this is some problem with the app config settings. Because there is a "new" app config var called "ANDROID_SIGN_APP". Which is set by default to "false". And this variable is used to call the ant command. But if you run an ant command with "ant debug" (which will be called if "ANDROID_SIGN_APP" is set to false), it automatically inserts the android:debuggable="true" attribute, while "ant release" does not. So you have to set "ANDROID_SIGN_APP" to "true" if you want a release build. |
| ||
Oh well. What if I want to use my own sign script? Does that one works with JDK 1.7? |
| ||
Same problem here... But where should I put the new line "android:debuggable="false"?${ANDROID_MANIFEST_MAIN} <application android:label="${ANDROID_APP_LABEL}" android:icon="@drawable/icon"> ----> HERE? android:debuggable="false" ---- <activity android:name="MonkeyGame" ----> OR HERE? android:debuggable="false" ---- and what about the new advise " Set ANDROID_SIGN_APP to true"? Where should I do this? |
| ||
I managed to upload by filling in the signing stuff in v75 and setting to release mode when I compile. |
| ||
Here:${ANDROID_MANIFEST_MAIN} <application android:label="${ANDROID_APP_LABEL}" android:icon="@drawable/icon" android:debuggable="false"> |
| ||
Thank you, Xaron. I tried it your way and it seems to work. GooglePlay has accepted the apk file. |
| ||
You're very welcome! :) |
| ||
Strange - I did nothing and Google Play accepted my game. Maybe it's the way the apk is being signed? I always open the project on eclipse and sign it from there... |
| ||
If you sign your app through eclipse, it does call "ant release" for you while it recompile the project. I did some test and found out, that all apks before Monkey V73 were build with debuggable set to true. No matter if it was compiled in release or debug mode. So you have to use Monkey V73+ and the built in signing script. I doesn't know any way to sign the apk with an own script. And it is necessary to set: ANDROID_SIGN_APP=True Google has changed the restrictions to upload an apk. They denied debuggable apks. |