Is there any way to clone a project. I would like to make changes to a app that is approved on itunes with out my user base seeing tons of updates. I would rather roll it out when all the changes are made so the user only has to refresh once. Thanks

The capability to suspend the update feature for a specific application for some period of time while you are working on it. That would be a nice option to have. As long as the application functions correctly while it's update feature is supressed. Able to gather images, GPS or anything unrelated to control panel updates. Good Idea.... The core properties contains the following definition. When the app launches (or when it's brought to the forefront in a multi-tasking environment) it attempts to report to this URL. The primary purpose of this URL is to return a timestamp indicating the last time the app refreshed it's core settings file. If the timestamp returned by this URL is different that the last time it checked, it will trigger a method to re-download the app's main configuration data from the Configuration Data URL (see below). Leave this Report to Cloud URL blank if you don't want to check for remote updates.

I'm interested in this as well. The reason I'd like to do this is to completely COPY a project from one account to another. I'd like to have it available in a separate account so that others can have access to it in order to update it when needed, and I don't want them to have access to all of my other apps. Any quick fix, solution or work-around for this???

Sorry guys, Buzztouch doesn't provide a means of duplicating an app, ...and as far as I know, there isn't an esay workaround available. It would be cool though if one of you wants to build it. ;) As far as updating the app goes, it seems you may have painted yourself in a bit of a corner. It is really important to understand the different options available for the process of updating your app before releasing it to the public. That is why we always recommend people thoroughly go through the Documentation. We understand that users like yourself often just want to jump in and start building, but then sometimes you end up in a situation like this. If you feel that you can make the changes to your app quickly enough, you might be able to do that where everyone using the app wouldn't really see the 'messy' process of the update. You could also, as you've probably figured, create a nearly identical app and upload that as an update. The third option that comes to mind - If time isn't an issue, you could change the config settings to make the app no longer check for updates. Wait about a month for everyone (or a lot of people) to refresh to the 'disconnected' app, and then make changes in your control panel and upload the update. The idea behind having an app that checks for updates is that it helps with the building and debugging of the app. It's also useful in the situation where the structure of an app is finalized and you just want to update content from time to time.