I recently signed and published my game in the Android Developers Console and I’m having problems updating the apk file. I created a new VersionCode and a new Version name in my Android Manifest but when I upload the new file it spits an error message “there’s already a Version 1 file” even though I changed the Manifest Version Code “2” and the VersionName"1.1" I’ve deactivated and unpublished it and I am still unable to upload the updated apk. file. I changed my keystore file and changed the name of the apk file and it just won’t upload with out giving the same error “there’s already a VersionCode 1 file.”
I’m working on Windows 7, Unity 3.2 ,downloaded APIs for minSDK 2.1 -2. 3.3
Does anybody know how to “update” a published apk on the Android Developers Console?
thanx for your help!
see attachments(photos) my manifest and errors on console
Version Name/Code values in AndroidManifest.xml are overwritten by “Bundle Version” and “Bundle Version Code” from Player Settings
(so you have to change them there)
The keystore that I originally created was created incorrectly. I put my zip code instead of the Country code which I assume should be “US”. Then when I created a “new” keystore with the same alias and passwords and try to upload to the Developers console, I recieve an error message. " you must use the same certificate as the original." The keystore is the problem because the user is unable to download the game on their phone. When the user downloads the game they receive an error message that says " the certificate was signed incorrectly" What do I do?
The error message from the user says “the keystore is not signed correctly”. Any suggestions? I created the apk on Unity 3d and the keystore is created within that program. One other thing. I used/checked the “copy protection” in the Developers Console. This adds about 20 megs to the app. Could this cause conflicts when the user downloads?
Yes, you must use the key store you created the first time when you published your app. If you lost/overwritten it, then you are out of luck. You will NEVER EVER be able to update your app.
There are more then enough hints on the Android Developer page/references that you must carefully secure (and make multiple backups stored on multiple locations) your keystore. Once lost, it can never again be restored. Neither by you nor by Google.
As for Copy protection: Never use it (why in gods name did you even checked it on? It’s clearly marked as deprecated feature and you get told in red letters to use licensing service instead). It’s a feature which was broken from the beginning and caused quite some havoc when developers published an app and the with an later update changed the setting.
This prevents people form updating (the installation will fail or crash), because apps with copy protection will usually be stored in /data/app-private folder (only root and the OS have access here) while non-protected will be installed in /data/app by default (not considering the SD installation, and apps with copy protection can’t be installed on SD card iirc). The only way to solve this (when switching back and forth) is telling the user to fist uninstall his app, before he installs the update. Which can be quite hard, if you have no in-app system to notifiy your users.
However, it can be possible that copy protected apps can’t be installed at all on newer OS’s, I don’t know. This feature was already deprecated 2+ years ago, when Android 1.5 was released (which was the version when LVL (License verification Library) was added).
One rule you must remember is: If you don’t have ANY IDEA what a feature does, DON’T USE IT and get information first. In worst case you will have to turn it off, accept that all of your users who downloaded the copy protected version will get pissed cause they can’t update and give you negative ratings.
I made those changes. Unmarked copy protection. My users are still receiving an error message while the app is installing at about 80-95% downloaded it spits an error message “package not signed correctly”. I’ve published several “new” test applications and I know the apk is signed correctly. I created a new keystore. Changed the name of the package and I’m receiving the same error. I’m doing something wrong? Does anybody have any ideas? thanx
Please look at my manifest. Posted earlier. Is this a possible problem.?
Am I missing something in the script? thanx
thanx!
