Asked this before without an exact answer. So - If I want to update an app I published for android, is there an equivalent to the iphone's process of going to itunes connect, telling it you have an update coming, and describing what's new in the update. Or do you just push another APK to android market and it appears magically, updates on everyones device without telling them what's new about it? Steve

Well I know why you didn't get a straight answer. Because you can update CONTENT via Buzztouch since all your data is on a server. However, the actual CODE, cannot be updated without creating a new build (same way you made the original build). Go to iTunes Connect->Apps->Your App->Add version bottom right. Go through the process. Like most things apple. It's very simple/easy to follow.

I think you misunderstood. I know how to update iPhone apps. I asked this in android forum because I don't know if for android there is the equivalent of going to iTunes connect, updating version number, giving description of what's new, etc. I don't see anywhere in android developer page to add a version and add a description of what's new.

Hi Steve, When I published an update to my Android app, this is what I did (using the new control panel...not the old version): * Log into Google Play Developer Console * Click on the app you want to update * Click the APK section on the left * Upload your new APK. Hit publish if it's ready to go * Click on Store Listing * Make whatever changes you need to reflect the new version. If you click in a field and modify it, the "Save and Publish" button will display near the STORE LISTING header. Hit it when you're ready to publish. * Celebrate because you've updated your app! Mark

Hi stevek, here is a quick read on the subject http://support.andromo.com/kb/distributing/how-to-update-your-app-in-google-play cheers! ian

Ha! or do what Mark said:)

Great find, Ian! I think I need to update my How To Submit to Google Play doc with information on doing updates. Mark

Thanks, all. I'll try it tomorrow. Steve

Ah, well from readin' your post I gathered you we're talkin' iOS and was saying that you had already done it with Android. Anyways, sorry about the confusion. -tM

Mark, Once I change the version number in the xml file, do I just go ahead with exactly what you have in chapter 9 of your great tutorial, or do some things have to be changed. For example,when you sign for release, do I still create a NEW keystore or use the previous one created for the previous version? ( I understand absolutely nothing about these keystores). Steve

Hi Steve, Yep, you've got it! Just increment the version, put whatever you want as the version string, and sign with the same keystore you used the first time. That's actually a requirement. If you use a different keystore, Google will see it as a new app, and not an update. Mark

Mark, And do you use the old keystores for both steps, the debugging and the release? And do I really have to do the debug step at all? Steve

You can use whatever keystore you want for debugging...the default debug.keystore is fine. But when you sign your apk for uploading to Google, it MUST be with the same release keystore you used on the original version. That's the only requirement that counts. If you have Google Maps API keys configured in strings.xml, just leave them as they are, since nothing surrounding those should have changed. Bottom line is, create the updated apk using the same release keystore you used for the previous version, and you'll be good to go! Mark

Mark, OK. We'll see what happens. Things rarely go smoothly the first time around. I'll keep my fingers crosses. You'd think both Apple and Google would figure out a better way. Steve

Hi Steve, I suspect it'll work out fine. I actually think Google has it right...you make updates to your app, create an apk with the same credentials as the earlier version, and upload. Pretty straightforward! Mark

Knew there would be trouble. So I first take my new updated app, change the app version code and name to 1.1, set debuggable to true and go through the debug routine. I did exactly as in the article, using the existing debug keystore in the Android folder and everything went through and I saved it. Then went back, changed debuggable to false, and started to go through the exporting, and then after next it tells me that the debuggable is set to true, even though it is false. I quit, go back to the xml file and sure enough it is set to false. But now I see a red x next to the Name entry which is SkyEventFinder_appDelegate. I click on this red x and get the following message: Class com.skyeventfinder.SkyEventFinder_appDelegate does not exist. What's going on? Steve

First try a Project...Clean. If that doesn't work, try deleting your project from Eclipse, and then loading it again. Mark

I already deleted and reloaded. Clean doesn't work. Before I try again, 1) do I have to do the debug signing and can I go directly to release. 2) and if I do, should I use old keystore for the debug too, or, as I did here, create a new one with the debug.keystore in the Android folder? Steve

You only have to do debug for debugging. So, just use the release key. And change the debuggae=false directly in the manifest file. Mark

Before I do that I'm getting an error that version code doesn't allow floats . I put version code and version name as 1.1 What's this all about and how do I then change to a version 1.1?

OK, I read that version code should be an integer, so I'll just change it to 2.

OK, so I can have no red x's. Export, and get to keystore selection, and I pick to use existing. Then choose the old version release keystore. Put in password, then hit next. Get a screen with key alias on top and underneath a red x and the warning "Invalid keystore format." Then I cannot under existing keysore which is checked under it, choose an alias. What do they mean invalid keystore format? Steve

What I should say is i put in is the previous release.apk Is this different than the keystore?

OK., found the distrib.keystore on my desktop. Put it in and now get the message that keystore was tapered with or the password is incorrect. The password is correct. What to do now? Steve

Hey Steve, Well, unfortunately, I don't know if any way to recover a tampered with keystore or recover the password. Are you absolutely, 100% sure that the password is correct? You don't have caplocks on or anything like that? If the keystore is corrupt or you can't recall your password, then you basically have to create a new keystore to sign the app with, which then make it, in the eyes of Google, a new app, and not an upgrade. So, people will have to uninstall the old one and install the new one to get the new content. I'd make sure that you know without a doubt you have the correct keystore and password. If you use the Eclipse Keytool Plugin, you can try to open the keystore there and see if it's good. My YouTube channel has a video on how to install that plugin in Eclipse. Going forward, you should be super careful about the keystore you sign your apps with. Put it in a place you know for sure, and back it up. Make sure you have the password recorded somewhere. You can use the same keystore to sign multiple apps (just like with Apple and their certificates), so you really only need to create one unless you have another reason to create multiple ones. Mark

Mark, Just went ahead and unpublished first app, refunded money to the two who had bought it and told the it would reappear in an hour or so (though they can keep the old, perfectly operating version if they want), and resubmitted. Back on line in an hour! Not too painful. Imagine if this were an Apple app! - I'd probably be still tearing my hair out. Steve

Mark, Just want to confirm on something you said. I made three android apps and made 3 keystores as i went along. I have lost one of them. Are you saying, when I go to upgrade that app in the future, I can use any of the other 2 keystores I have saved? Steve

Hi Steve, To upgrade an app, you can only use the same keystore that it was signed with last time. The keystore is a means that Google uses to sign your apps, to say that they indeed come from whom they say they do. Otherwise, other people could publish an app claiming that it comes from you. Not a good thing. My method is to create a single release keystore that I sign all my apps with. That way I only have one keystore to manage, and if I'm careful, back it up, and make sure I don't forget the passwords, I should be able to do updates with ease. Mark

Mark, Just want to confirm on something you said. I made three android apps and made 3 keystores as i went along. I have lost one of them. Are you saying, when I go to upgrade that app in the future, I can use any of the other 2 keystores I have saved? Steve

Mark, So if I understand correctly, since I lost keystore1 which I used when signing app1, if I want to update app1 I cant use any other keystore I may have. Right? Steve

That is correct. Each keystore is unique. If you loose it, and you've signed an app with it, then you basically have to publish a new version of the app with a new keystore (or maybe use one of your others). Google won't allow an update if the key used on a previous version doesn't match with the update. At least that's how I understand it from my reading of the Google documentation. Mark