We're seeing the same thing in the wild. Security Scoped Bookmarks on macOS 15 don't resolve after a while. Reports are that a device restart helps, but only for a little while. Trying to gather more data from some pretty angry users right now... Same app/binary works on lower macOS versions. App is a sandboxed. Something is very broken resolving Security Scoped Bookmarks on Sequoia. Edit to add: Same error is indicated (256).

Cheers @eskimo, works a treat!

No worries, here you go: FB13548312

That's exactly right on all counts @eskimo. In the "NG" case as you call it, we see the connection remaining in .preparing state, with no changes or updates ever received afterwards. So, we're just left hanging. This is reproducible in the code posted above. Are you able to see the same?

Hi @eskimo If you install your app on a ‘clean’ machine, one that’s never seen it before, does it reproduce the problem? Yes, it is also reproducible on a 'clean' machine. I'll raise a DTS if that's the best way to fix this. Thanks.

Hi @eskimo - Sorry if I wasn't clear. This is happening on all machines that we are aware of, we have a broad customer base through the App Store and we have received word from some of them about this issue, I expect a lot of people won't notice or care. I don't believe this is a specific machine related issue. So: We do not see our App Name on any machines generally It's missing on all machines we are aware of Can you tell us what factors go into the system determining what "App Name" to display there so I can try to debug it myself in some way? Is it just CFBundleDisplayName? or are other factors involved. I'm also happy to share the App or Testflight with you so you can see for yourself on your own machine. Just let me know (I can mail or whatever).

No, tiny test prokect is all good that way (See image). Code below: let lac = LAContext() lac.evaluatePolicy(LAPolicy.deviceOwnerAuthenticationWithBiometricsOrWatch, localizedReason: "Blah") { success, error in print("\(success) - \(String(describing: error))") } This is happening on a lot of people's machines (Sonoma and Ventura for sure), we're getting reports, but it's quite cosmetic so no one really minds too much, but obviously we'd like to fix.