icloud

This question already has an answer here: Prevent iCloud sync of data (using .nosync?) 6 answers Is there a way to prevent your application data (Documents folder contents) from being synced to iCloud? (other then storing it in Caches directory because of the new issues in iOS5 with doing that ) My Application has need of storing data on the device, but for security reasons it can't be synchronized to any 3rd party (including Apple). From: https://developer.apple.com/library/ios/#qa/qa1719/_index.html You can use the following method to set the "do not back up" extended attribute. Whenever you

Issue: When choosing a document from iCloud the application randomly crashes, for most of the time the following code will work, but on rare occasions it will fail. I have enabled iCloud entitlement in the app and can't seem to find the reason why it intermittently fails. Is there a check that I'm missing? It's also hanging for a noticeable 5 or so seconds on occasions (usually in the run up to crashing) Code: #pragma mark - iCloud ======================================================================================================= - (void)documentPicker:(UIDocumentPickerViewController *

I am having this issue where I save something to the icloud using CloudKit but immediately fetching the results doesn't return the latest data inserted. Example let todoRecord = CKRecord(recordType: "Todos") todoRecord.setValue(todo, forKey: "todotext") publicDB.saveRecord(todoRecord, completionHandler: { (record, error) -> Void in NSLog("Saved in cloudkit") let predicate = NSPredicate(value: true) let query = CKQuery(recordType: "Todos", predicate: predicate) self.publicDB.performQuery(query, inZoneWithID: nil) { results, error in if error != nil { dispatch_async(dispatch_get_main_queue()) {

I am having the problem, that URLForUbiquityContainerIdentifier is returning nil in some cases even if the user has set up everything correctly in the settings. My code: dispatch_async(someQueue, ^{ if (![[NSFileManager defaultManager] URLForUbiquityContainerIdentifier:nil]) { ErrLog(@"iCloud container not available."); return; } dispatch_async(dispatch_get_main_queue(), ^{ [...] }); }); Does anybody came across the same problem? I am setting nil as the container identifier which should work according to the Apple docs, but I am not so convinced anymore about that. Also this code works fine

I've read the Apple docs and Ray Wenderlich's tutorial. It seems that I'm forced to use UIDocument so I read it up in the docs. I've found that it's effective to use Document-based approach. My problem is I don't want to be tied in techniques specific to the platform (iOS) thus my app has its own models made from scratch that only inherit from NSObject. This includes saving/loading. Now, I need to integrate iCloud along with my old models. How will I do it in an elegant/effective way where I get to keep my old model implementation and be able to integrate iCloud? You are not in any way forced

I am trying to use iCloud Documents to store XML files from my iOS App. Everything seems to be working fine (I can write and read files without errors) except my App's files do not show up in iCloud Documents neither in icloud.com nor in developer.icloud.com nor on my Windows PC in iCloud Drive folder. I was running the app in simulator and tested with TestFlight on a real device. I have the latest version of iCloud for Windows 4.0 installed. The App is created in Xcode 6. Does anyone know how to make the files appear in iCloud Documents? The code I am using for the saving the file: NSLog(@

I am using iCloud with Core Data, based on the SQLite "Library-style" application design as specified by Apple. While the basic functionality works very well, I am concerned about the transaction logs and how they are managed. While the database for my app is not large, it is very active and the core data stack is saved many times while the app is in use. I have noticed that a new transaction log is created for every core data save. The end result is that I have a TON of transaction logs and they take up much more space than the actual database. 1) Do the transaction logs ever get