So I just re-downloaded the source for my app so that I could do an update as I had made saves to changes of the old version and it did not work and messed up my whole app. The only problem, is that is now being saved as a different package. When I try to change it in the Manifest it screws up the whole application. How can i change my Package name back to the old one so that I can update my app. Thanks in advance!

Hi MM2000, If you've made changes to your app, the only thing you need to update (aside from adding any new local files, images, etc), is the config file. You don't need to download the source at all. Just do a Show Configuration Data...copy all that info...paste it into your current local config file, and then compile as normal. Given the recent updates to the site, though, I would make sure that the first few lines of the new config file are the same as for the old config file. Just in case there is any weirdness related to the site transfer. Mark

Which version of Buzztouch are you using? Fred

@Mark, Unfortunatly it is too late, as I've deleted all my old source code, and replaced it with the new downloaded one before I could realize it. Could I go into my control panel, rename it to the orginal package name, download that source, re-upload it, then go back into my control panel and again rename it so that the correct name appears on top of the app? @Fred i'm using BT 1.4 BTW thanks guys for helping me out with mapping, I finally got everything figured out!

If you re-download the source code, Not sure this makes a difference: with the orginal setting And you get the same package name You can update the app in the Android Market. As far as it's been proven you can't change the package name in a BTv1.4 app.

Howdy, Let me start out by saying that, for v1.4 and v1.5, the only thing that changes when you make changes to your app is the configuration file. That assumes you don't change the name of your app, or change the icon. That being said, there is no need to download new source after making changes to your app. Like I mentioned above, all you need to do is update your local config file to match the online one, then recompile, test and submit. If you've changed the name of your app, then what you mentioned above I think will work. The jist of it, for Android, as I understand it, is that the "package=X" line in AndroidManifest.xml has to match what's already in the store. Hope this helps a bit. Don't be deleting any more source packages in the future...you don't need to! Mark

Well when i redownload the source, it saves it as a different name. I just renamed my app in my control panel to the old package name, and then dl the source. Going to see if that works...

If you can't get the orginal package name, depending on how much skill you have you could possibly recover the orginal package from your computer. Remember nothing is ever truly erased on a computer. Fred

The source package name itself doesn't mean anything...you can call it whatever you want. It's what's inside that zip file that counts! Mark

@fred, yes i know, but I really don't want to go digging that much... @mark yes that's why i changed it through BT control panel, and didn't just change the name of the zip file...

Mark, the problem is related to how Buzztouch names the package name. It can't be changed in BTv1.4. If by going back to the orginal Buzztouch App name in the Control Panel can you get your orginal Package Name. Is the Buzztouch App Name the only variable? User name? Fred

Well, by package name, are we talking about the actual zip file that gets downloaded? Because the name for that file, pre-new web site, was based on the project name, BT version, and app ID. But I don't think the name of the zip file has anything to do with anything at all. Eclipse just cares about what's in the AndroidManifest.xml file, and some associated files. If the project name was changed, then the manifest file will change, and a few of the other files as well. That, would, be a problem. Mark

It's all very confusing because the same name is used varoius times and package name means two similar but different things. The problems is not the name of the zip file downloaded from Buzztouch, and as you point out in the scheme of things it's not important. The Package name as found in the manifest is set by Buzztouch and can't be changed in BTv1.4. I didn't know till now that changes in the Control Panel resulted in a new package name. Big Problem if you'd like to update your App in Android Market. Fred

Agreed. The package name that we are interested in is the one that's specified in AndroidManifest.xml under package=. That's the one that's important. And, yep, it cannot be changed in v1.4. Mark

Yes, but now the question is, ''How isr it set?'' What are the variables? Fred

For v1.4, it looks like this: package="com.v1_4.BC9E983BDA5912A772F721ED.com" For v1.5, like this: package="com.azfishingspots" For v2.0, like this: package="com.azfishingspots" Thus, it appears that v1.4 is the only version that uses the app ID as part of the package name. The other two versions use the project name. Mark

Mark, that's exactally the problem. Where does the app id get set? Can we control the variables in setting the id? Fred

No...we don't have any control in setting up the app ID. From what I can tell, it's a random ID created when the project is initiated in the control panel for the first time. The app ID should not change, even if the project name does, from what I can tell. Mark

Easy way to find out is to experiment. Create a v1.5 app with whatever name, download the source, check out the ID in the configuration file. Rename the project in the control panel, download the source, see if it's the same. Mark

Is there a way to upconvert from 1.4 to 1.5? How else can I fix this problem? I was able to pull my old source from my recycle bin, but i'm getting the geopoint error again after I follow all the steps for getting the maps to work

If you recovered the source code with the orginal package name you're set. Many have created maps that's easy. Fred

No way to migrate from v1.4 to v1.5 without recreating the app from scratch. Mark