Thanks, Quinn!

I don't think the second snippet would be fixed by writing NSString *ns = (__bridge_transfer NSString *)CFBridgingRelease(string); because as far as I know, __bridge_transfer is basically the same as CFBridgingRelease. The problem with the second snippet is that when the local variable ns goes out of scope, the string will be released, but the local variable string is not set to nil, hence CFRelease will be passed a bad pointer.

For notarizing, you should use a "Developer ID Application" certificate.

You should send that request to Apple using Feedback Assistant, a more official channel for such things.

I've never seen the problem you describe, but if the Issue Navigator panel isn't working, you could look in the Report Navigator. But also use Feedback Assistant to file a bug report.

I don't speak Swift, but the frontmostApplication property of NSWorkspace should give you what you want.

When I try using the "short link" method in the accepted reply, the Mac App Store app goes into an infinite loop of "Cannot Connect to App Store" error messages.

This is not the place to ask Apple to fix a bug. Use Feedback Assistant.

Have you gotten as far as getting an NSURL from the drop? Once you have that, create an NSBundle from it, and then can get the bundle identifier.

If you want to release "without hosting to app store", why would you select App Store Connect?

There are several kinds of "daemons" and "agents" that can run in the background on macOS. Here's some documentation: Daemons and Services Programming Guide

Try calling CGRequestScreenCaptureAccess before the other stuff. That’s probably needed to do screen capture from within the sandbox.

Is your executable an application? Is it code signed?

What have you tried, CGDisplayCreateImage? You may also need CGPreflightScreenCaptureAccess and CGRequestScreenCaptureAccess.

In https://developer.apple.com/download/all/ you can find "command line tools for Xcode 14.2".