@Etresoft - thank you! That is heartening. I've done some more digging. I think the biggest one that I haven't found an answer to is (a) can I automatically create folders within the security-accessed folder and (b) can I launch a background process that could access my project folder (and its internals) Is there a good recent swift code or article - I can't seem to find something my newbie mind can handle.

I figured out the issue. The culprit was a forced Swift try! which failed. It was working on my dev account because the folder/file being read from existed but didn't in other accounts. Hard lesson learned. The crash logs, debug symbol all turned out to be useless in indicating where the issue was.

Hi @Claude31 - yes, for my purposes I need to be able to load entire text files. It is supposed to be a "Text Editor" so I was hoping they had done basic performance tests against it. It certainly seems to be doing something wonky with every keystroke (I am not doing anything - haven't attached any listeners). I will raise a bug, thank you. Hopefully they'll improve the text editor with more capabilities and better performance soon.

If anyone else comes here: The solution proposed by stakes worked for me on macOS BigSur.

I'm having similar issues but in macOS! Updating to macOS 11.3 w/ Xcode 12.5 messed up my existing app which worked just fine in previous versions. How is it that Apple hasn't fixed this. update: tried the EmptyView() and it doesn't help. Clicking the navigation link still leads to a "unable to present, please file a bug" error. Frustrating.

I am dealing with the exact situation with no resolution from Apple. App worked just fine (macOS parent-detail view type app), and then I upgraded to Big Sur 11.3, and it broke it. Now clicking the parent NavigationLink gives me "unable to present" error and the behavior is absolutely erratic when I try to nail down any issue. Wasted hours only to find out others are having similar issues. I haven't found a workaround, and the app is dead for users with 11.3. Really frustrating.

Did you find a solution? Dealing with exact same on macOS after upgrading to Big Sur 11.3. Seems like a Swift framework error. The workaround mentioned did not work for me.