APK not signed correctly
bernardo.chuecos
Member, PRO Posts: 75
I have signed my APK using the gamesalad APK singer and uploaded it to the Play Store following every single step. I can download it in my phone just fine and so can many of my friends, however some people have been complaining that they get the error "APK not signed correctly", and when I try it on my brother's tablet I get the same error. I tried to use earlier versions of JDK as they said JDK 7 and 8 do not get along with the play store too well, but that did not solve the problem. I've looked and looked and some people here seem to have the same problem, but no other posts have a solution. Does anyone know how to fix this? If not, is there another way to sign an APK that is not through gamesalad?
Comments
We use the command line tools provided with the Android SDK, that's why you have to set the paths to them. You could sign your apk manually, but it would be using the same tools and command lines we use.
Can you give us some more specific information on which device/os configurations are having an issue? We've tried many different combinations and not had a problem. If we knew the app name we could also try using your app and not ours.
My brother's tablet is a Samsung Galaxy Note 10.1 running android 4.1.2, and one of the people who complained was my friend who has a Samsung Galaxy S3 Mini. My phone (in which the game installs just fine) is a Samsung Galaxy S5 Active running android 5.0. I was thinking maybe the problem only happens with older versions of android OS? and my game's package name in the Play Store is com.bcgames.skies
I forgot to add that before I published it, I had the same problem with my unpublished versions in my brother's tablet, but I was able to fix it by creating a new Key every time I signed it. However I cannot do that anymore since the Play Store requires me to use the same Key every time I update my game. The problem seemed to originate every time I used the same Key to sign an app more than once.
The game seems to have the same problem on android 4.0.4 as well. It seems to be the older versions of android that reject gamesalad's signature
We're looking at it.
If you find out the solution please let me know, I do not wanna lose such a big portion of the market because of this
There's a fix for this in 13.36 which should be released soon. I'll make a longer post then that explains what to do and why it wasn't working.