Hi, I have app on appstore and the problem is that when I open app there is no last changes which I made, but when I refresh home screen then I have newest changes and this is ok. I think there was some old configuration in cache which I upload and now it is first old config and after refreshing new configuration came. I need to solution for that, is there any way to auto refresh app while app is opening (some tip in configuration file or something like that). I need fast solution because app is on appstore and it is bad image. thx Nick

Hi Nick, I'm assuming this is for Apple. And I'm also assuming that you made changes to your app AFTER you submitted it to the appstore (or, you submitted it with an old BT_Config.txt file). That would be the reason it's being refreshed when people open it for the first time. If you're app is online...meaning the URLs for Configuration Data and Report to Cloud have been configured, then this will be an ongoing problem for you. But, it's also a feature of buzztouch, in that you can update your app without having to send an update to iTunes. Give this document a read to understand the differences between online and offline apps : http://www.buzztouch.com/resources/Understanding_App_Refresh_and_Offline_Apps_v1.0.pdf One way to solve this is to submit a new version to the app store with the latest BT_Config.txt file included, and then don't touch anything. New users, and updating users, will get the new app and no refresh will be required. But, then you need to figure out what to do going forward. Mark

Hi Mark, thank you for your fast response. My app is online which mean if I made some changes on BT server app ask me to refresh but I find out that if I install app after the changes made on BT server app will not ask to refresh which mean all new users will see old configuration and old content. I need for first aid that all users which install app when app start or auto refresh or if app ask to refresh any tips for that?

OK...well, it's odd that it's not working. But, here's what you should try: * Go to the configuration panel for your app, and click on Manage Core Properties. * Click on Report to Cloud URL, and there click on Use the default buzztouch URL. * Click on Configuration Data URL, and there click on Use the default buzztouch URL. These steps ensure your app is configured to report to the buzztouch servers and see if there are updates and, if there are, download them. If you had something different configured, then you may need to send in an update to the store with these new settings to get it to work for all users. Did that help? Mark

Doesn't work, if I update new archive at appstore with new BT_config.txt how long I have to wait to approve?

It'll probably take into next week for it to get approved. There's not much else you can do here. If your app is currently configured to not check the buzztouch servers for updates, or not check some other location for the BT_Config.txt file, then it has no way to get any information to tell it to now go and check for updates. The only solution for what I perceive to be your problem is to create an update to the app and submit it to the store as soon as possible. Make sure you have the latest BT_Config.txt file in Xcode, and run a Product...Clean before you build. If you get it in the store today, I bet by mid next week, it would be approved. Mark

Thank you Mark, I think I will upload new version and wait till then I need to change something daily then users will update app. :) Thank you again for help and fast response

Mark, for off line apps would it be a best practice to include an Update screen that the user could select to update? If this is possible that how would it be setup? Assuming app is on iTunes. Place latest api on Dropbox. Then ? Paid vs. Free app? Fred

Hi Fred, That's a very interesting suggestion! I'm not sure how that would work, since the BT_Config file is compiled into the app, and I don't know if it's writable when the app is installed. I'll check into it! Mark

Just some musings to past the time. Concept : How to have user check for update. Have HTML form that would compare latest config file or version name/number with installed version name/number. Suggest check for update after certain time period or user selection. Have app check for update. If latest version returns, You have the latest build. If update is available then it returns, Update is available with appropriate link to Dropdown. Place latest config on Dropbox or latest apk or ipa on Dropbox. Don't think it'd be necessary to place config file there since the form would/court be checking version name/number that you could enter on the form and on the online form Fred

Appreciate the musings, Fred! Seems like few problems to solve in the forums today...guess everything is working perfectly! Your idea seems legit for sure. I pinged @David, and he suggests that writing to the config file in a published app is doable, but not very easy. So, that would be one hurdle that would need to be overcome. I'm not entirely convinced there is a need for this though. If the app is online, then using the standard update mechanisms should be good enough. If it's offline, again, using the standard update mechanisms should be good. I can see the utility in this if for some reason a person messes up the Data/Report to Cloud URLs for an active app, but then I'm not sure how it would get communicated to the user, since they're effectively offline. Certainly some stuff to think about here. Mark

Yes, I see your point, but a daily, weekly, monthly ( choose your time period) would avoid the delay in updating via App Store. If you haven't used the app for some period of time ot might be useful. Using the version number/name avoids the not easy to compare / write to config file. Just from users perspective they'll be happy they can verify latest build. Fred