When I use the UIDocumentPickerViewController with kUTTypeFolder I am only able to pick from the providers built-in to iOS/iPad OS, such as On My iPad, iCloud Drive, network shares and USB drives. As of beta 4, 3rd party providers are shown, but disabled (not selectable or browsable).I have not been able to find any information on whether or not 3rd party providers will be supported by the release of iPad OS 13. I am hoping this will be possible in a future build (or at least something 3rd party providers can enable) since this is a big driving factor for enabling us to ditch a *lot* of custom cloud storage code.Any info (or if anyone knows either way) would be much appreciated!
Post not yet marked as solved
Is anyone with a UIDocumentBrowserViewController-based app able to use the simulator? I have a document-based app that I am updating for iOS 13, but I cannot get *ANY* locations working in the iPad OS 13 simulator. I am able to use "On My iPad", iCloud Drive, and 3rd party providers) on a test device running iPad OS 13 (but since I can't update all of my devices to the beta yet, this is really hindering my ability to test with different screen sizes). I have tried several iPad simulators with the same result -- Even with iCloud Drive enabled, the only options I get under Locations are "Connect to Server" and "Edit Sidebar". No iCloud Drive, no "On My iPad", and the "Connect to Server" option immediately pops up an error: "The operation couldn't be completed. An unexpected error occurred."
Post not yet marked as solved
I am trying to find the right solution for migrating existing apps to be document-based apps. They all make heavy use of Core Data as well as store additional content that the user imports. UIManagedDocument seemed like a no-brainer, since it provides UIDocument support and has APIs for "Additional content", however the documentation states that "Additional content is not supported in iCloud". The primary motiviation for moving to a document-based app is to allow users to store their documents anywhere, including in the cloud, so this is obviously concerning.I cannot find any additional details on this stipulation, primarily:Is this referring to the deprecated iCloud Core Data, or does this also preclude storing "additional content" in managed documents that are stored on iCloud drive? The call to writeAdditionalContent() appears to be using NSFileCoordinator (based on the call stack), so I am hoping this is just for iCloud Core Data, but I cannot find any mention of it elsewhere.If the "additional content" API cannot be used with documents that can be saved to iCloud Drive, is there a recommended solution for storing both Core Data and custom content inside a document package (e.g. override writeContents, or subclass UIDocument and manage the core data stack myself)? All the guides recommend using UIManagedDocument.I can't imagine I am the only one trying to do this, so any help would be much appreciated!
litkyle.