I store a total of 4 files in an app's iCloud container, the content for each is an archived NSDictionary. The files range in size from about 2KB to 2MB.
I have a single ULDocument subclass which implements readFromFileWrapper:error: and fileWrapperWithError:
I use NSMetadataQuery to monitor the status of these files so users know what's going on.
I have a Mac & iOS version of this app, both share the same ULDocument subclass.
Sometimes saving a document works fine. The change is promptly uploaded to iCloud and promptly downloaded on other devices. However, I'll often save a document, after which I'll receive an update notification from NSMetadataQuery indicating that the document is now uploading, with 0% uploaded. Then, there will be a long delay (if see it take over 5 minutes) before I see any additional updates from NSMetadataQuery. Eventually, uploading does continue and complete. The problem occurs in both clients. The problem seems to happen more if I save a document frequently. The problem affects all 4 files equally, but not necessarily simultaneously.
My users tend to jump around on their devices frequently, which of course leads to conflicts when this problem is occurring.
I actually doubt this problem is ULDocument, I'm almost certain it is iCloud Documents, but since you have experience with both I figured I'd raise the issue.
Is this a problem that was encountered when using ULDocument, or iCloud Documents in general, in Ulyssess or Daedalus and are they still using this class?
I store a total of 4 files in an app's iCloud container, the content for each is an archived NSDictionary. The files range in size from about 2KB to 2MB.
I have a single ULDocument subclass which implements
readFromFileWrapper:error:andfileWrapperWithError:I use NSMetadataQuery to monitor the status of these files so users know what's going on.
I have a Mac & iOS version of this app, both share the same ULDocument subclass.
Sometimes saving a document works fine. The change is promptly uploaded to iCloud and promptly downloaded on other devices. However, I'll often save a document, after which I'll receive an update notification from
NSMetadataQueryindicating that the document is now uploading, with 0% uploaded. Then, there will be a long delay (if see it take over 5 minutes) before I see any additional updates fromNSMetadataQuery. Eventually, uploading does continue and complete. The problem occurs in both clients. The problem seems to happen more if I save a document frequently. The problem affects all 4 files equally, but not necessarily simultaneously.My users tend to jump around on their devices frequently, which of course leads to conflicts when this problem is occurring.
I actually doubt this problem is ULDocument, I'm almost certain it is iCloud Documents, but since you have experience with both I figured I'd raise the issue.
Is this a problem that was encountered when using ULDocument, or iCloud Documents in general, in Ulyssess or Daedalus and are they still using this class?