I'm having kind of a weird issue, and I'm not sure what's causing it. I'm currently trying to reduce the size of my config file, so that app refreshes won't cancel out. However, I'm finding that new users of the app receive a screen not found when they access a menu item (immediately after the first download). If they are able to refresh the app, it gets fixed, but new users won't know this, plus its a bad user experience. I've already received another bad rating, so I want to nip this in the bud. My app is FISH FINDER. Could you by chance take a quick look? Much appreciated!

Hi Hoogler...I've been monitoring some statistics on your app for this exact reason. There are a few dozen 'out there' that have very large amounts of content like yours and each of them is showing similiar symptoms. It's looking like the file size is for sure the problem (the configuration data file) when on 3G. I commented on this http://www.buzztouch.com/forum/thread.php?tid=1AD9F87E170CC1DE4D3E627 post a few minutes ago with some thoughts about this too. I havn't been worried about your large app because I thought you had removed the need for the control panel and the config data was being compiled and submitted. This alone will solve the problem. As long as the app doesn't need to fetch that massive file, all should work. It sounds like it's trying to refresh from the server..not sure why?

It just seemed odd that they would have to refresh immediately after download. I'm just worried that if I remove the data url now, users will never get to retrieve their data. I've been meaning to remove the dataurl, but I wanted to add some locations first. But I think my priorities have changed :P

They don't have to refresh the app's core data immediately after download but could be refreshing a menu instead. If a menu has a dataURL it will try to fetch it's content for the rows when the screen loads. This is probably what's happening. It sounds to me like you should remove ALL dataURLs from all the menus and screens and compile the thing with the giant config file. The idea would be to totally prevent it from looking online for anything. You'll also want to remove the reportToCloudURL so it doesn't look for updates and then ask the user if they want to refresh.

Sounds good. Sounds like I have my evening planned :) Again, thanks for all the help David. Quick question though. How will my live app be affected if I remove the data url? Should I remove my app from the store until the update is approved?