I tried Quinn's program once more under macOS 14.5 on my Intel-based Mac, and saw flowsw instead of 10 TCP sockets. So it appears that the difference is Sonoma versus Ventura.

Yes, the Mac App Store mandates sandboxing, but no, sandboxing does not prohibit Accessibility permission. In fact I have two apps in the Mac App Store that can request and use Accessibility permission.

I did the test again on a different Mac on the same local network, this time running macOS 14.5. And then I saw the flowsw thing instead of 10 TCP sockets. Another difference between the machines is that the one running Ventura has an Intel CPU, while the one with Sonoma is M1.

By the way, since the skywalkctl command was recommended here, I want to make a couple of comments about it. First, it can only be run using sudo. Second, the man page says you can get help on a command using skywalkctl COMMAND help, but that doesn't work.

I tried Quinn's test program, and I did see 10 TCP sockets. MacOS 13.6.7. I have iCloud+ but had Private Relay turned off. (Private Relay is part of iCloud+). No VPN.

The documentation of NSWorkspaceWillPowerOffNotification says To receive this notification, use notificationCenter to register for it. If you use a different notification center to register, you won’t receive the notification. That is, when you add the observer, you need to use NSWorkspace.notificationCenter instead of NotificationCenter.default.

In the first approach, do you see your imported certificate and private key under "My Certificates" in Keychain Access? Do you see your imported certificate in Xcode's Settings > Accounts when you click "Manage Certificates"?

When I grep the sample code project for vImagePiecewiseGamma_Planar8, I get no hits. So in what sense is your code a translation?

Is the array allocated on the heap (e.g., with malloc) or on the stack? In the latter case, you may be exceeding the available size of the stack.

I ran your file through plutil and it said Encountered unexpected character k on line 23 while looking for close tag That is, you're missing a left angle bracket in the string tag after CFBundleShortVersionString.

Does your command line tool have an embedded Info.plist? I would guess that Accessibility access is recorded by bundle ID.

https://developer.apple.com/download/all/?q=xcode

Quoting the NSUserDefaults documentation: Important Don’t try to access the preferences subsystem directly. Modifying preference property list files may result in loss of changes, delay of reflecting changes, and app crashes. To configure preferences, use the defaults command-line utility in macOS instead.

An app for the Mac App Store must be a single app package, but that package can contain nested helpers of various kinds including app packages. And an app store app can contain a login item, but I was told that it can't be required. I think that's in the review guidelines somewhere. My app AutoPairs has radio buttons in the user interface, where one can choose to run the program only when the UI app is open, or always when logged it. I don't use XPC (I use distributed notifications and shared user defaults), but I think you can. You'll be signing the whole package, including any helpers, with the same app store signature.

@Justin said: Typically we would expect to see objc_msgSend at the top of the stack trace when a crash occurs due to messaging a deallocated object. Since I originally wrote this post, I updated my app to be universal, and I'm still getting these crash reports. Here's the start of the backtrace, now showing objc_msgSend: Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 libobjc.A.dylib 0x19f716290 lookUpImpOrForward + 72 1 libobjc.A.dylib 0x19f715f64 _objc_msgSend_uncached + 68 2 AppKit 0x1a3453e54 -[NSControl currentEditor] + 56 3 AppKit 0x1a344ba14 -[NSControl _setWindow:] + 48 4 AppKit 0x1a34ee160 -[NSSegmentedControl _setWindow:] + 52 5 AppKit 0x1a3ebbeb4 __21-[NSView _setWindow:]_block_invoke.146 + 268 6 AppKit 0x1a34344a4 -[NSView _setWindow:] + 1780 7 AppKit 0x1a3ebbeb4 __21-[NSView _setWindow:]_block_invoke.146 + 268 8 AppKit 0x1a34344a4 -[NSView _setWindow:] + 1780 9 AppKit 0x1a3618a70 -[NSWindow dealloc] + 684 A full crash report: crashlog2024-04-14 08-21-26.crash