Hi there, I’ve also been receiving crash reports to my app that seem to point to the same cause as yours. NSOutlineView on macOS 15 crashes in NSConcreteMapTable, [_TtCs12_SwiftObject isEqual:] (and isSubclass in my cases). I've also sent Feedback with my case FB16913684. FB16913684: NSOutlineView crashes by checking isSubclass internally on macOS 15

Sent feedback: FB18401945.

If this is the case, I'd like to see the feature in SwiftUI in future SDK. So I sent a feature request: FB18743468.

After my post, I found NSPopUpButton (or NSButton) has a private API named semanticContext for this purpose. Though, I can’t use it since my app is distributed in the App Store... cf. https://stackoverflow.com/questions/79593493/how-to-achieve-grouped-form-styled-controls-using-appkit/79607626#79607626

I’m facing a similar issue with arm64e on macOS. When I turn on the Authenticate Pointers feature for my macOS app target on Xcode 26, the app target prompts requiring the 'arm64e-apple-macos’ target, the same warning message as the original poster, for local swift packages using in the main target and the target is no longer able to build. @WangZiYuan If you received any personal response from Feedback Assistant, could you please share it? @DTS Engineer Is there any way to detour it? Should I create a new post in this forumn/feedback? My environment is: macOS: Version 26.1 Beta (25B5042k) Xcode: Version 26.1 beta (17B5025f)

Oh, sorry. I realized the feedback number mentioned in my original post refers to a wrong one. I meant FB20432458.

Since there appears to be no existing solution, I filed it as feature request: FB21012567.

@Etresoft You can use the "isReadable" value from URLResourceValues. Thank you. This is exactly the API I was looking for. However, it sounds like you're not approaching this from the right direction. I'm not trying to open random files...; I just want to use it to prompt the user to obtain access permissions if they don't have them for the file they tried to open (the file linked by an alias).

@DTS Engineer Hi Quinn, thank you for additional information. However, I suppose checkResourceIsReachable() returns true if the file exists, regardless of whether it can be accessed. What I want to know this time is whether the app can open that file in a sandbox environment.

Thank you again for your quick response! I understand that this may be an issue on the macOS side and that, unfortunately, there is no available workaround at the moment. I hope this behavior can be addressed in a future update. I also appreciate you sharing the background behind this phenomenon. It’s technically interesting to me. If you’re able to reproduce not-returning case, a sysdiagnose log from that might yield a useful insight. OK. I’ll send additional information, including a sysdiagnose, if I’m able to reproduce the not-returning case.