Just about to submit app to iconnect had no screens error before, have fully tested app in simulator and in device, copied over latest bt_config file. Taking BT Davids advice ran console on section with a image gallery of 15 pics I got the following in console 2011-09-07 00:24:36.329 ponyfun[443:707] BT_fileManager: File does exist in Xcode bundle: welsh_ponyd.jpg 2011-09-07 00:24:36.336 ponyfun[443:95ab] BT_fileManager: File does not exist in cached directory: Australian.jpg 2011-09-07 00:24:36.363 ponyfun[443:8d23] BT_fileManager: File does not exist in cached directory: chincoteague.jpg 2011-09-07 00:24:36.465 ponyfun[443:707] BT_screen_images: viewDidAppear 1) Does first line 'file exist' show that the images I have copied to BT_images are in bundle 2) File does not exist in cached - is that anything to worry about. Any help gratefully received as I find xcode very confusing and only want to submit when 100% certain all is OK

Hi Marko, If you've tested you app in the simulator and device, and all works well, there is no need to replace the config file. You only really want to replace that file if you've made changes to your console and want to ensure that the project you eventually submit to apple is the latest and greatest. If you make changes to the console after submitting to Apple, but before it is approved, they will be prompted to refresh the app when they go to test it, and you'll get rejected (assuming default Report to Cloud and Data URL settings). So if your app is ''finished'' and tests fine, no need to update the config file. If when you fire up your app and you are prompted to refresh, then you do need to update the config file. 1) yes, at least for the file: welsh_ponyd.jpg 2) Probably not. Does it test fine in the sim/device? Cache is used to help images (and other data) load faster the next time it is accessed. For example if you had an image accessed through a URL - The first time the image was loaded it would need to visit that URL and download the image to display it. That might take a little while depending on the file size, and internet connection of the user, etc. But, after that image is downloaded for the first time it is stored in cache. So the next time that image is loaded, it doesn't need to visit the URL, it can load the image directly from cache, which is usually much faster.

Thanks Parker that really helps, the Buzz touch environment is so user friendly that once you step out of it on to xcode you feel a little bewildered. Form David, Yourself and other users I am starting to understand the mechanics of how apps work and there file structure. PS Parker is the coolest character in an UK children's TV show called Thunderbirds

Addding here for reference. @Marko: You are right, the console shows that it IS finding the image in the Xcode bundle so it's not expecting to find them in the cache. The cache is where it would expect to find them after downloading them from a URL (if you used image URL's instead of adding to the project).. The code does this for images and documents... a...if the file is found in the bundle, awesome, use that. It's been added to Xcode and compiled with the app. b... if it's not in the bundle, is it in the cache? If so, cool, use that, it was previously downloaded and saved to the cache for offline use... c... if it's not in the bundle, and not in the cache, get it from the URL and save it to the cache for next time This logic works all over the place for files, images, audio files etc. Sounds like you're getting the hang of understanding the console output - awesome - major timesaver when you're trying to figure out what the heck it's doing!

Thanks David - I feel part of the Alumni for the Buzztouch University of Apps and my thesis is getting App on istore.