I want to upload a new apk file for my android app. I first tried to do it on my old laptop and couldn't because i couldn't figure out how to change the version number. Then I got a new mac, installed eclipse, downloaded the new code from buzztouch, and then created a new apk file. Then i got two errors, same version number error, and different keystore file. So a emailed a copy of the original release.keystore file, created a new apk file, and i'm getting the same two errors. Anyone have any idea what i'm missing here? Would love any help I could get.

It's all in the AndroidManifest.xml file. Check out this tutorial: https://www.buzztouch.com/forum/thread.php?tid=C2FCEFDC22B3A9C1ADABE3B If you still have questions, let me know! Mark

Not sure what's going on with your keystore exactly, but you can change your version number by opening up the AndroidManifest.xml file in Eclipse.

To do an update to an app, you must use the same keystore you signed it originally with. Once you make the version number change in the manifest file, and sign it with the same keystore, all will be well! Mark

Agree with Mark. Just not sure why you'd be getting an error if you emailed the original keystore to yourself. Hopefully the updated version number solves both problems though.

Thanks guys. Tried everything, still same problem. I don't remember being ask to provide an alias name before? t

Think of a keychain like a password protected dictionary. The dictionary consists of keys called "aliases" and values called "passwords". So, you will have two passwords, one for the keychain and one for the alias. Each app is associated with an alias, and a keychain can hold multiple aliases (apps)

Ok I get it. Thanks Chris. I will have to copy and paste the exact error later when I get home so I can get some guidance. Right now I'm totally stumped. I emailed myself the release.keystore file and used it. But when I upload to the play store it tells me the key is different. It shows me the current set of numbers and letters. Then it shows me the one I'm trying to upload, and it is different. I can't see the number until I upload the apk file.

Is it possible you used a different keystore on the app originally, or overwrote that keystore after you uploaded the app?

If its really named release.keystore, my guess is that you accidentally overwrote it with another app.

You have to use the same release keystore you signed it with initially, otherwise Google considers it a new app. There's no way around that unfortunately. You can use the Eclipse Keytool plugin to verify signatures of the keystore. Mark

Is the a way to manually plug in the original number?

I've only made one app. I have two files, debug.keystore and release.keystore. I can't even update the apk file using my old laptop now. I'm really don't know what else to do except rename my app and start over?

Unfortunately, this is the one part about Android that is frustratingly locked down. If you can't get the original keystore to work, then yes, you'll have to rename it and submit it as a new app.

Thanks Chris. I appreciate your help.

Yep, Chris has it nailed. The whole point of the keystore is to validate...or certify...the originator of the app. If at any time it doesn't match, that means the originator of that update cannot be verified. That's pretty important stuff, because you want to make sure your apps are coming from a trusted source. If you've only ever created a single keystore, then it's weird that it's no longer working. Try the Eclipse Keytool Plugin to see if your keystore is corrupt or anything. Here's a video I did showing how to install that: http://www.youtube.com/watch?v=IaXE2FUENFI Maybe all that will help you remember the password or alias! Mark

Cool. Thanks Mark. I like your notebook plugin by the way. Works perfect for an app I have in mind.