App Store Connect shows all ratings in the App Store. The client side App Store only shows ratings for your country.

How did you find this? And more importantly, what other sample code or Apple documentation pages exist that have no referencing web page?

I did try the approach of moving it into the PlugIns directory and still App store expected me to codesign all the dylibs and the binaries with entitlements. Certainly. Here is an ancient post that may still be relevant for you: https://stackoverflow.com/questions/16960662/embedding-a-java-runtime-into-a-sandboxed-cocoa-mac-app It may be possible to just slap entitlements on the binary. I don't know. Another option could be to integrate the runtime into your executable. And finally, take another look at the license costs for the .NET version and keep that in mind as your burn hours trying to get Java to work.

There is a WWDC 2025 video on how to manage Apple-hosted or self-hosted assets. See https://developer.apple.com/videos/play/wwdc2025/325

Exactly what problems are you having? I reviewed those QT instructions. They don't look too bad. However, your build scripts are significantly different. In particular, you're trying to use brew. Brew can be useful in some cases where people just want to download some open source tool on their Mac and run it without thinking. But if you're going to distribute something, especially on iOS, it should be considered a non-starter. Trying to build both iOS and Mac versions of a framework using command line scripts can be very challenging. There are lots of subtle problems. You're essentially doing a cross-compile. It sounds like so many people have done this that there's good support for iOS. That's considered the default. So it makes sense you would have trouble with an oddball platform (relatively speaking) like macOS. If you can get the source into a true Xcode project, it would be much, much easier to build multiple platforms. For the record, ffmpeg is a challenging project. I did need to incorporate ffmpeg into a project myself a few years ago. Even on a major linux distribution, I still had to make changes to the ffmpeg source to get it to compile. You seem to be taking the correct approach, just trying to do too much at once. I recommend starting over with the original QT instructions. Go more slowly this time. Don't try to build both X64 and ARM. Build an xcframework just for iOS. Then add macOS Apple Silicon, which should be very similar. I expect all the complications would be from the X86 build. ffmpeg definitely supports that, but many low-level compilation settings, and maybe even source files, will be radically different.

That’s cool tech, but you still need a Java runtime to run the Java side of this. That's a disappointment. I hereby retract that recommendation. Instead, I suggest trying the Aspose Email for .NET package. I know nothing about .NET, but it seems there are some ways to incorporate .NET libraries without a .NET runtime. I sure don't understand .NET versions. But there is a much larger community of people using .NET on macOS than Java.

This entire setup (JAR + JRE) is bundled within the Contents/Resources directory of the macOS app Don't use the Resources directory for executable code. Maybe try the "Frameworks" folder instead? I know it says "Frameworks", but it is an older directory that is likely to be more compatible with something unusual like this. According to the current documentation, there is also a "PlugIns" and a "Library" folder that are possible. But I think these are intended for specific artifacts. The "Helpers" folder is another catch-all possibility. A better idea might be the new Swift/Java interoperability project.

is an xcframework an appropriate approach for this? It sounds like a Swift Package would be a better idea. You could include the xcframework and define any external dependencies, as described here.

The app is successfully notarized and stapled, I packaged it in a .dmg using hdiutil and went ahead and notarized and stapled that as well. You don't need to notarize both. If this is a stand-alone app, I recommend just notarizing the app and distributing it as a ZIP file. You don't really need a disk image at all. The only times where a download actually worked with no problems was when I downloaded through the terminal using curl, The curl tool won't add the quarantine attribute. That makes it avoid Gatekeeper altogether. Problems like this are usually because of some runtime check. There is a new tool called "syspolicy_check", as described here, that is supposed to help with that. Are you building in Xcode? This is a common problem, but occurs most often to people who aren't using Xcode. If you are using some 3rd party build system, I recommend you put your efforts towards porting to Xcode. This makes lots of problems, including notarization, go away.

the Fast User Switching button was available in the Control Center's "Edit Controls" UI. So there may be a minor bug there. I've always had Fast User Switching enabled. But after Kevin's description of the changes, I understand your confusion. I am a developer and encountered this problem in my development workflow while trying to bring my apps to macOS 26, so I had reason to believe it might be relevant for others. Perhaps I'm wrong, but my understanding has always been that this forum is for developers to seek help with any issues they encounter while testing the betas. I've never known that the discussion should be limited strictly to APIs. Back when Apple last re-launched these forums, they explicitly described them as "meant for code-level questions". But at the same time, they seem to have removed any limitations on posting so that people no longer have to be members of the developer program. And beta questions still aren't allowed in the Apple Support Community, which is meant for end users. Normally it is an Apple-identified bot (or bot-resembling post) that kindly asks a spammer to spam in the other forums. So therefore, I assumed you weren't a developer. But in all honestly, even those posts are preferable to the majority of posts in this forum that are simply complaining about Apple's App Review and developer program practices, which I can't do anything about. So, yeah, I get frustrated with a "discussion forum" full of questions that are impossible for any non-Apple employee to answer. I've had poor experiences using VMs to go forward in versions. Even installing a beta version in a VM requires a change to the host OS, which then makes your developer system slightly non-standard. I prefer to run betas, and often the current version, on a dedicated test machine. The time I save more than pays for the extra hardware costs.

First of all, Fast User Switching works fine. Secondly, I'm not sure what you mean by "secondary volume". I don't recommend trying to test with any kind of unusual boot configuration. You're liable to waste a lot of time writing up bug reports that way. And finally, Fast User switching is an operating system feature. I'm unaware of any 3rd party developer API that might affect its behaviour. Therefore, it's not relevant to this developer forum.

What do you mean by "the sandbox"? Do you just mean the Xcode sandbox feature or are you talking about a Mac App Store app? The difference is very important. Since this path is outside the sandbox, obviously your app (and its child task curl) can't access it. That's the whole point of the sandbox. If this is some purpose-built, quick-n-dirty app, you could probably just give yourself a temporary sandbox exemption. Or just turn off the sandbox. If this is a Mac App Store app and/or you want to do it the "proper" way, then you'll need a user interface to allow the user to select the socket. PS: You might also consider ditching curl entirely and just making the connection yourself.

Technically speaking, SceneKit is only "soft deprecated". It is in maintenance mode and will only receive major bug fixes. Apple said there are no plans for a hard deprecation at this time.

Sorry, I'm just a regular person. I can't do anything about what Apple does or does not post. But I looked into this a bit more and I can confirm that it isn't a panda at all. It's a fox. This is the Fox 2 sample from WWDC 2017. Later, this sample was used again in WWDC 2021 to demo physical and virtual game controllers. However, the code for those changes seems limited to the "Code" tab.

To clarify, I think completionHandler on runAnimationGroup should specify that the closure is sendable. It seems like that would fix the problem. But regardless, the above code will work and is backwards compatible.