This is really crazy to me. I finally get a new version of my android app running, test it on my nexus 7 and it works like a charm. I then go to export it to the Google play store by hitting export, and signing it with an old keystore from a previous version. It goes on through and sets up the APK on my desktop. In Google play I import the APK and it seems to update. The new version in now showing, the app is "in Prod" immediately (I've never seen it go so fast) I then delete it from my nexus and go to the Android appstore and download the app. First weird thing - the splash screen is the new correct one but I get the BT message that the app has changed, do I want to refresh. I say yes and immediately an old, incorrect splash screen is there. And when I go into the app, basically nothing is working. So I delete app again and re-download. This time I say no to the refresh, and though some screens work, some do not, though they all worked on my device when the app ran in Eclipse. This is very frustrating and again I have a broken app out there in the wild. Please help. Thanks P.S. Don't know if it makes a difference but forgot to change the config file to live mode before publishing so it's still in design on the store. Steve

Just out of curiosity, if you delete the app from your device, and then load up the version again directly from the apk instead of via Google Play, what happens? Still old content? Mark

Mark, How do you load up directly from APK.

The easiest way is to send it to yourself via email and click on it, or use DropBox or something. You can also install it via adb (Android Debug Bridge)...you can easily Google for instructions. Mark

Mark, when I loaded it from the APK it works! What gives? Steve

That's hard to say. I'm assuming the package name in the AndroidManifest.xml file is the same as the previous version, and that you incremented the version. And that you signed it with the same release keystore you did the first time, so that it would be recognized as an update to the previous version. Have you tried loading the original version on the device, and then updating it via Google Play instead of installing from scratch to see what happens? That's what customers are likely to do. Strange situation for sure. Mark

Mark, A little more information. The previous version was BT 2 and I recompiled it, with a different name under the BT core for Android v3.0 Though it has a new name, I used the old keystore since I was under the impression I could use that not just for this app but for any app. Google Play accepts it as an update, updating the version, etc. I did submit it in design mode but don't see why that should make a difference. Unfortunately, I deleted the old app from Eclipse so I cant download it to device and then update it in Google Play. This is driving me crazy and my app is out there making the few who've bought it probably very mad. Steve

Mark, get this. I deleted the app again and re-installed from Google Play and now it works! Before I get my hopes up, is it possible that APK I downloaded is still hanging around somewhere and that's why it works? I'm a pessimist by nature. Steve

The odd thing is this: "I recompiled it, with a different name under the BT core for Android v3.0 Though it has a new name, I used the old keystore" You can use the same release keystore with multiple apps. That perfectly acceptable. For an app to be recognized as an update to an existing app, the package name (i.e. com.stevescoolapp) has to be the same. If you compiled with with a different name (i.e. com.stevesnewapp), that should have been seen by Google as an entirely different app. If that's not the case, then I really have no idea why not. That rule seems pretty clear to me (and validated through experience). Lots of things could be going on here I guess. One thing I think you need to fix immediately is the Design mode config file. If you leave that, than any changes you make in the control panel will immediately get reflected to the app. Also, I could see problems if the original version is in Live mode. I haven't updated an app on Play for a while. Is there a way to deactivate the old version of your app, and make sure the new one is the active one? Mark

>Is there a way to deactivate the old version of your app, and make sure the new one is the active one? I don't think it is possible to delete the old version of an app if there is at least one active user / download. You can only unpublish it and you will see it in your console but nobody will see it through Google Play. Simultaneously you should publish a totally new app (as far as Google is concerned), which will be a new version of your old app. In this scenario you are losing all the metadata about your app, including the number of downloads. You are starting from scratch, so to speak. If this were a totally new app then it almost didn''t matter, but if you had 13000 downloads in one app as I did, that it did matter. Still, I had to forgo the existing app and start afresh, and now the app has additional 60000 downloads and I am in total control.

"Unpublish" - that's the word I was looking for! If you are updating a current, active app, you don't want to publish a totally new app (at least from the AndroidManifest file perspective). Otherwise, it'll be exactly that...a new app, and not an update. However, I suspect there are some reasons why you want to create a new one instead of an update. But, in general, it's best to stick with an update if you can. I wrote a tutorial a while back on the manifest file...some of the explanation is valid in this case : https://www.buzztouch.com/forum/thread.php?tid=C2FCEFDC22B3A9C1ADABE3B Not sure if any of this helps your problem, Steve! Let us know if you're still having issues! Mark

Everything seems to be working now. Can't explain it but am happy. Thanks all for the help and I'll be entering a few things I did to eliminate some problems I had with blank htm pages in a new post just to let everyone know what worked for me. Steve