We ran into this rejected too and wound up having to provide default data for everything. I know, it seems weird to have this wealth of data out there on iCloud and everything seems to be leading to cloud based data, but (apparently) it's gotta run for those hold-outs that don't want to use it. You might actually have to provide some recepies in your bundle and update them to your local storage from CloudKit.The scheme that I used is to always refer to local storage for any views and run the update process as a background operation. The update process overwrites/adds to the local storage so it's available on the next read. It simplifies the code not having to worry about which source you're using at the time. This also covers the 'occasionally connected' scenario. If you allow the end user to write to the data then you'll need to make sure you don't overwrite something they changed. Perhaps store their notes in separate annotation file(s).HTH,Mike
Topic:
App & System Services
SubTopic:
iCloud & Data
Tags: