Unsigned Apk of Signing the Apk button VS Download Apk button
BigDave
Member Posts: 2,239
There are two options on the publishing page to get the unsigned .apk
1. by signing the .apk you always get the unsigned with it
2. by hitting download .apk
The second option creates an unsigned .apk with a weird long number in front of the file name.
I recently used this option to update an existing unsigned .apk on the amazon App Store.
Now I have a user complain to have lost all his save games with the last update. If he hasn't a specific problem/or deleted it by himself it makes me to assume that even after removing the number in front the unsigned .apk's are not 100% compatible
Can someone confirm or dispute?
Comments
I don't know all the internals of how the Amazon store works when you upload a file, but as far as I know the name isn't important, the identifier and version of the bundle are. So, if you have two apk files with different names, but the identifier is com.bigdave.coolgame then Android will consider them to be the same file.
You get the same apk file when you click sign or download, and the signed name is whatever you choose.
@GeorgeGS thanks
This seems to relate to your other thread. This sounds like a keystone issue. Do you by chance have two key stores?
@Lost_Oasis_Games this is kind of related as I tried the other publishing method to avoid signing (which doesn't work right now). And I made an game update with this unsigned APK. I was just unsure if this option is clever to use or not. Still treeing to make the signing work again. Just updated OS X. If it doesn't work i will have to figure how to downgrade Java..