For my app LatinToGo, it is on the app store, say I wanted to make it offline, I would have to edit some codes in Xcode and on my buzztouch control panel, BUT what will happen to my live app on the app store? I plan on using the same application build that is currently live to make it offline. I want to know what will happen to my live version on the app store while I am tweaking a new version. Please let me know, Thanks

It could be a big mess unless you do it correctly. Read Online vs. Offline www.myskylla.wordpress.com Pay attention to the part about predeploying your app. Fred

Fred, let's say I make a NEW app, do I need to worry about anythinge else then? If I work from a NEW app?

That's certainly a possibility but I can see how to do it in Android with BTv1.5 and BTv2.0, but I'm not certain how to do so with iOS. Unless you're upgrading to BTv2.0 it's not necessary to go that route. Try the following: Predeploy all embedded content Update on App Store After App Store update is published deploy new embedded content. Submit App Store update with new config file. Now that app offline. Fred

Ok, and If I decide to make the current version offline, is that also fine? Instead of making a new one and adding gamecenter and all those features again.

Perhaps I misunderstood your initial question. Take app offline Make tweaks update config file in app Publish Take app back online.

I want my current version on the app store to be offline, can I just take out the cloud URL ONLINE file and it's offline?

That's one way has certain consequences you probably don't want. Better method is to put config file on Dropbox and point to it. By doing so you could take app back online for new tweaks. Fred

Do you have a tutorial of this? That would make it much easier to understand? Thanks

Read Online vs. Offline www.myskylla.wordpress.com Pay attention to the part about predeploying your app. Fred

Hi Raoul, Answered your email, but will answer here as well. You can obviously create a new, unique app that is completely offline. To do that, just remove the Configuration Data URL and Report to Cloud URL from your Core Properties screen. That prevents the app from checking in anywhere for updates. If you do that, any updates have to be delivered via the appropriate market. Having an app offline does not affect things like URL based screen or other resources...those are still available (assuming a network connection). Taking a current app offline is pretty tricky, and I think not advised. The problem is that if you take it offline, until the app checks in for a refresh, it will still be online. So, until every instance of the app checks in and downloads the config file that then takes offline, some percentage of your users would see any changes you make to the control panel. The best strategy is to go offline from the start. Mark

GoNorthWest: So if I take my app off the app store, all I would need to do is DELETE the Data URL and Report to Cloud URL from my core properties screen? That would be all? I will contact Apple and ask them to take my app down for less than a week and see what they say then. Just to be clear, thats ALL I need to do correct?

If you want to take your current app offline, you have to remove the Data Configuration URL and Report to Cloud URL from Core Properties. You can either supply that as an update to the BT_Config.txt by directly modifying the one in your download package, or you can remove them from the appropriate fields in the Core Properties section of your app's control panel. Either way, however, there will be, for a period of time (that could be a long time), a certain number of people who will not have checked in for the update, and thus will see any new changes you make to the app until they download the latest config file. You may or may not care about that. In my opinion, taking an app that is already published offline is pretty risky. There will be people who will see changes you make, even if you do not intend them to. And, if you take it offline, the only way to get it back online is through a store update. My recommendation...if you have new content you want to add, create a test app that only you can see to test that content. Once it's tested, implement it in the current published app. Mark

Would you consider this: I will submit an OLD version to app store, then once its approved, I will delete the 2 URLs in the core properties for the new version And submit that NEW one to app store? So basically online and offline is depending on the cloud URL and data URL only?

But the problem is your making the assumption that EVERYBODY who has installed your app will rush out and update it the moment they see one available. I know people who take ages to update their apps, so you cannot guarantee any particular timeline on when it would be safe to make changes in your control panel again. Mark

Ok, but am I correct about the offline and online apps depend on the data URL and cloud URL? So once I delete them, it would be offline?

That is correct. The Report to Cloud URL is where the app checks in to see if there is an update. If there is no URL there, then the app cannot check in. Thus, it's offline. The Configuration Data URL is where the app gets its config data from. Remove that URL, and it uses the last version of the file it has as the config file. Remove both, and it's entirely dependent on it's most current config file. Mark