Hi everyone, I have an iOS app that uses a DocumentBrowserViewController. According to the documentation, I should be able to set the contentTypesForRecentDocuments so that when the document browser shows "Recent", it only shows a certain type of documents (a subset of the types of documents that the app can open). Also according to the documentation, "You can define a subset of these types using the UIDocumentBrowserRecentDocumentContentTypes key in the app’s Info.plist file." I have tried several ways of setting the UIDocumentBrowserRecentDocumentContentTypes key in the app's Info.plist file, but I could not see any changes in the behaviour of the document browser. Alternatively, is there any way to tell the DocumentBrowserViewController to not start with "Recents"? It's extremely confusing for new users.

I have an iOS app, based on the Documents Browser. That app has an iCloud folder, following all the instructions (NSUbiquitousContainers dict in Info.plist, and so on). As far as I can tell, it works for most of the users. But some users report that, after creating a file in the document browser window, they meet a "file not found" error and the app does not load the file. As far as I can tell: the files are created (the counter is incremented, I've see error with "Untitled 3: file not found"). FileManager() sees the files in question. somewhere inside the app, opening this file fails. How can I fix this? I'm not sure about the prevalence, but it seems to be rare but very annoying for the affected users.

Hello, this is very weird. I have an app where I use UIDocumentPickerViewController(forOpeningContentTypes: [.folder]) to let the users access to directories that are in the sandbox of other apps. It's been working since iOS 13. On the beta versions of iOS and iPadOS 26.1 (betas 3 and 4), the second time the UIDocumentPickerViewController is presented, it becomes unresponsive, with a spinning wheel in the top right corner where the "Open" button should be. I have absolutely no clue what the issue could be. It doesn't seem to be a widespread issue, but I have also no idea on how to find the origin and fix it. As far as I can tell from the debugger, this line is executed: DispatchQueue.main.async { rootVC?.present(self.documentPicker, animated: true, completion: nil) } and then nothing else happens.