I have a great app created from BT 1.4. I'm nearly complete creating an "update" to this app using the new BT tools. My question is: since I had to create a "new" app using the new BT tools, how do I make sure it will be recognized as an "update" on my customers phones? I don't want users to have to delete the app they have, and then go get the new one - I'd prefer it work as an update. I've googled a bit and read about Bundle Identifiers, and making them the same should cause iTunes to see it as an update. Just a little nervous, and I do plan to test it out on my phone. Has anyone ever had a 1.4 app they had to recreate in BT 2.0 and publish as an update? Did it work with just matching the Bundle Identifier between the two?

I have done updates from 1.5 to 2.0, and the users did not experience any major issues. Jake

I have 1.4 android apps. can you shed some light on the process to update these apps? Joe Sprott Bodacious Media

I've successfully completed this about a month or so ago. For iOS, it is a matter of setting the bundle identifier of your new app to match the bundle identifier of your 1.4 app, and incrementing the version number. I suggest testing this on an actual device (not your own developer device installed via XCode - that does not replicate an actual end user app update). I tested this on an actual iOS device by provisioning a colleague's iPhone to allow apps to be installed from my developer account (instructions for doing this can be found in Apple's iOS developer documentation). I compiled the app for ad hoc distribution, and sent it to my colleague. They installed it on the phone via iTunes, and we watched to see if the app updated. If it replaced the app, the test was successful. If it installed separately, it was not successful. The only issues I recall in my testing were with how I provisioned my colleague's phone (we had errors in testing and incorrectly assumed it was because of the app I made, when in fact I had not properly provisioned their phone). For Android (3.0), your Application Package must be named to match your 1.4 app. For me it was a bit tricky, because I had this very long and rambling application package name (I think BT created it for me, and I just left it): "com.v1_4F3B2CbA7....D5.com" (all those letters are wrong, I'm just trying to give you an idea). I had to right click on the package in the Package Explorer of Eclipse, hover over Android Tools, select Rename Application Package, and carefully paste this value. Eclipse then did a bunch of churning, and that was it. After incrementing the version number, I sent the app file to my colleague, who successfully installed it on their phone. Hope I didn't leave anything out, but this is all I can recall from my efforts.

Thanks Peter Joe