Hi BT team, Thanks for all this, the app is up and running, it s really great ! (vedett league app) I just have question: i ve installed the app from the AppStore and when I open it for the first time it just shows a dummy menu. The normal content only shows up when i hit the refresh button. Once i do that, it stays normal. Is there a fix to this ? Thanks for everything, Jean-Louis

Hmm... this doesn't sound like a very good user-experience (as you realize). There are countless ways to configure the data-source for your app. I'll be this is happening: a) App launches and errors trying to read the BT_config.txt file (not sure why, just thinking this is why home screen is blank) b) Nothing else happens...until user taps refresh. Refresh forces app to fetch latest copy of config data from server - works. c) Next time app is launched the previously downloaded copy of data is used, which is OK. It's very likely that there is somethign wrong with the BT_config.txt file that is in Xcode. When the app is first installed, this is the file that is read. Can you see any trouble in the output console when the app launches? Maybe delete it from the simulator, delete the simulators cached download directory then reinstall. This should produce the same condition - blank screen. Before tapping anything else, look at the output Console for clues.

this happen to me before uploading your app make sure to download the source code again that will fix it delete your app from the simulator and download the s.code again insert your custom pics or backgrounds and install the app in your simulator again that will fix it trust me

Thanks for the tips ! Now that you tell me about it, it maybe did happen on the simulator, but once, and of course afterwards everything seemed normal. I'll try this and keep you posted (I'm amazed Apple did approve it this way, it works but still, like you say user-experience isn't top-notch now :)).

I too just experienced this. For some reason when looking in the console, there is never any call to the cloud to check the file. Once you force refresh, it's all good. The version that just hit the app store is based off of the 4/16/2011 release. Although, I never recall having this issue when I was testing the file on the device prior to submitting it. It possibly could be fixed by now. I'll follow up once I do a new compile.

I'll do the same, a new compile with the latest 1.5 version (uploading pics...great :)) and will follow up.

I just loaded the latest build to my device and am experiencing the same issue. I'm not certain what I should be looking for in the console that shows the task for comparing the included data config and the server data config. All I know is that at no point in the initial run is there anything about the data URL nor the date comparison I see if I've forced the refresh.

I think we've found the issue with this.... expect an update tomorrow.

grab the latest download...see if it works as expected. Bet it does ;-) Here's the logic: a) App launches for first time, no cached data, nothing to compare to. b) It 'reports' to cloud if it has a reportToCloudURL. This process saves a date-stamp to the device for comparison later c) Next time the app launches, it reports to cloud again. If server date-stamp is different than saved date-stamp (from last time) it alerts user for refresh. I DID find something wrong with this and you should be OK with the latest release I just put on the download server.

Great thanks ! I'll try it asap !

David, should this be notated in the change log as a new version or did you just overwrite the previous version?

It will be noted if it solves some issues discussed in this thread ;-)

Got it. In that case, it doesn't seem to have worked if I understand your logic list. Or maybe it did but not the way I think that it used to work. The first time the app loads upon clean install, there shouldn't be any notice of changes (even if there actually are). Only after the second time that the app loads there will be a notice of change now that there is a timestamp to compare to. Got that all right? If that is correct, it doesn't notice any changes that may have been previously made between the compiled download time and the first run time. Only if I make a change after the app has been run the first time will it then notice the changes. So, if I'm not actively making changes to the app, some users may never get that update notice. Unless of course they refresh the app themselves. Still with me? Just my thoughts on the logic.

Um... not with you. LOL. The only time the app won't check for changes is the first time it's installed and run. From this point on it should always have the time-stamp saved. When the app launches each time (or is brought to the forefront in a multi-task enabled device) it will compare this file to the result from reportToCloud. If they don't match it will advise. Maybe we're saying the same thing? Test this on the sim. Install app and make sure it's documents directory is empty. My sim saves files here: /Users/davidbook/Library/Application Support/iPhone Simulator/4.2/Applications/APP ID/Documents Your's probably does this same thing. Install the app, make sure this directory is empty. When it launches you should see a file saved to that directory. This is a plain text file and saved the time-stamp of the last refresh. If this exists, and is different from the value returned from reportToCloudURL it should advise.

So, the timestamp comparison is just looking for a change no matter newer or older? In that case, I understand the logic. And it appears that now that I understand the logic, the issue has been resolved. Thanks, David! BTW, what a good choice by your parents for your first name! Mine had the same idea.