Awhile back I posted on the forums asking how I could make a 2.0 app and replace my old 1.4 app in the android market as an update, without having it upload it as a new app (losing all download and rating stats!). I remember being told I couldn't, because the package names are different, so Google wouldn't allow it; and it's not so easy as to just change the package name and be on your way. I've figured it out though! And I'd like to share how step by step with you guys because I'm sure there are others out there wishing they could do the same thing. I don't use iphone apps so unfortunately, I'm not sure how to do it in Xcode. I've also only done this from 1.4 to 2.0, but I'd assume the steps would be very similar if trying to upgrade a 1.5 app etc. This tutorial will show you how to replace a 1.4 already in the market with a 2.0 app you've made as an update. [Scenario] 1.4 buzztouch app with package name com.v1_4.oldapp.com 2.0 buzztouch app with package name com.newapp ====================================================== 1) Import your new 2.0 app into Eclipse as you normally would. Make sure there are no errors before you begin. 2) Press Ctrl + H to bring up the search window, and choose the "File Search" tab. You may have to click the tiny arrows near the top to see it. 3) In "Containing text" type newapp (note: replace newapp with whatever your 2.0 package name is after the com.) then click on the Replace button. 4) After its done searching, in the With field, type in v1_4.oldapp.com and click ok. If it asks you to update launch configurations say yes. 5) Once it's finished, you need to remove your app from Eclipse. Once removed, open up the folder your source code is in, and navigate to the src folder. You'll need to create and rename a couple folders so your path looks like below: Original path: src/com/newapp/ New path: src/com/v1_4/oldapp/com/ When done, all the files that were in the original path need to be in the new path. 6) Open up the new path you created src/com/v1_4/oldapp/com/ and rename oldapp_appDelegate.java to com_appDelegate.java 7) Now reimport your modified app into Eclipse. Once imported, press Ctrl + H again to bring up the search, goto the file search tab, and type in v1.4_oldapp.com_appDelegate and click replace. After it scans and asks you what to replace it with, type com_appDelegate and hit ok. 8) Hopefully, if you did everything correctly, all errors will be gone and you can test the app! Now just open your AndroidManifest.xml and change the version number, and you should be able to replace the apk of your current app with the new one, and your users will be able to download it as an update. Also, make sure you compile the new apk with the same keystone you used for your 1.4 app! Enjoy :)

Excellent Fred

great job

A link to this tutorial is now in my Guide to Buzztouch v1.4 www.MySkylla.com Fred

@piggilypoo, this was a awesome contribution to buzztouch, thank you. David buzztouchmods.com

Great instructions, did you just figure this out from lots of trail and error? and even more importantly can these steps be used on ios and to port 1.5 to 2.0? This could be huge for anyone looking to move up a version. Great for stock apps with stock plug-ins. keeping for future reference. Thanks!

"and even more importantly can these steps be used onm ios and to port 1.5 to 2.0?" Was just thinking that! David buzztouchmods.com

and even more importantly can these steps be used to port 1.5 to 2.0? No, these steps allow you to rename a BTv2.0 app. (Should work with BTv1.5, may need some modification, but why use BTv1.5?) By renaming the BTv2.0 app you can replace the BTv1.4 .apk on Google Play. The problem had been that using the Android Tool to rename the package name didn't work.8 The solution outlined above solved that problem. For BTv1.5 simply use the tool found in "Android Tools" in Eclipse. For Android Tools simply right-click on the project. For BTv1.4 (iOS) I imagine there's a similar solution. The secret sauce is modifying the path. Fred

Followed all these steps, getting force close on all options...

Followed all these steps, getting force close on all options...