"Work together" in which way? Those are two totally unrelated apps with two totally different toolchains and project formats.
galad87
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution
Last seen
User for
Post
Replies
Boosts
Views
Activity
Safari stopped supporting NPAPI (and similar types) plugins in version 12.
But maybe someone out were wrote a Java Applet to Webassembly conversion tool.
[NSDocumentController.sharedDocumentController noteNewRecentDocumentURL:URL] or something like that.
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
Did you clone the git repository on iCloud Drive or another file storage service? That often doesn't mix well.
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).
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).
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 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?
Metal already have all the required API to implement raytracing. So probably there is nothing preventing Epic or Twinmotion from implementing it in Unreal or Twinmotion. However, to get good performance you will have to wait for an Apple Silicon GPU with raytracing acceleration.
Xcode 14.3 requires Ventura, I guess FileMerge deployment target was set to macOS 13.
You can use VideoToolBox API to list all the available encoders on your Mac or iOS device.
Yes, if the hardware supports it. I think 2017 or newer. Apple Silicon supports HEVC 10bit and 4:2:2 too.
Why the propertyListRepresentation? The kCVImageBufferAmbientViewingEnvironmentKey should be in the binary format defined in ITU-T H.274. So you should get the data directly as is and pass it to new buffer, a plist won't work.
Did you try to set the clip to bounds property to true?