I have relied on the call : NSSearchPathForDirectoriesInDomains(NSLibraryDirectory, NSUserDomainMask, YES); to get to the ~/Library folder which I then present to the user using NSOpenPanel Now suddenly, on macOS 11, the return path is to the library folder within the CONTAINER of the application. I don't think this is correct. It suddenly changes the behaviour. Trying to build the path starting from NSHomeDirectory() also does not work (again container). If Apple does not want to fix this, what could be a work-around? Thanks, Alco Blom

In my iOS app, I am using UIDocumentBrowserViewController as explained in several WWDC videos. I developed my app using the Xcode template : Document-based app. Now App Review is rejecting it (2x), because I use this concept. They write: "Your app also offers iCloud Drive file manager capabilities which is considered a primary feature. Users can share, delete, and add files in iCloud Drive through your app, and this is not appropriate for the App Store." I only show files of my own file extension (other files are dimmed by the browser), but one of the problems seem to be that the browser also shows folders. And the folders have a contextual menu, which shows commands like Delete. I don't understand their sentence 'add files'. Except, of course, there is the standard "Create Document" item. I can't seem to reason them and I think they are just wrong. How can I solve this situation? Many thanks, Alco Blom