Probably another victim of the clipsToBound change. NSView clipsToBound is set to false when compiling with the macOS 14 SDK. If the code drawing the button uses the dirty rect instead of the bounds, it will draw in weird way. Is that button image drawn by a subclass you wrote?

There is a similar (maybe?) issue that is replicable for example by opening Safari info window, and clicking on the Version or on the Copyright textfield. When clicked, the text will become blurry.

Probably you are signing it with different entitlements. It looks like your unsigned app is sandboxed, but when you sign it you use an entitlements file with sandbox disabled (or no entitlements file at all).

Try to switch back to the old linker. Xcode 15 ships with a new linker that might cause issues on older iOS versions (it definitely has issues on older macOS versions).

As written at the end of your message, altool is not supported anymore, it has been replaced by notarytool. https://developer.apple.com/documentation/technotes/tn3147-migrating-to-the-latest-notarization-tool?changes=_3_3

[NSDocumentController.sharedDocumentController noteNewRecentDocumentURL:URL] or something like that.

Safari stopped supporting NPAPI (and similar types) plugins in version 12. But maybe someone out were wrote a Java Applet to Webassembly conversion tool.

"Work together" in which way? Those are two totally unrelated apps with two totally different toolchains and project formats.

In my experience mouse tracking is so broken in macOS 13, and now even more in 14. I would write yet another feedback in the Feedback Assistant app.

You are calling some UIKit methods on a different thread. UIKit mostly can be used only from the main thread. You've got a NSURLSession that runs a callback on a background thread and then calls UIKit. The main thread checker is useful to catch this kind of issues.

The issue was triggered by thread 36, but you didn't post the stack trace of that thread, so it's not possible to know what's going wrong.

Of course, VideoToolbox will create encoded data with the specification of the format you selected. It will be decodable on every other hardware.

Video range means that black is 16 and white is 235, then there are super black and super white, that were historically useful when you had to color correct the video and restore missing details because the image exposure was not the best one. How are you converting from YpCbCr to RGB and back? Are you converting back to limited range or to full range.

The executable is trying to load some unsigned libraries from /usr/local/opt/, that can't be loaded because it was signed with the hardened runtime enabled. Maybe there is a way to do a static build with that library included? I never used gfortran, so I can't help more than this.