Apple always e-mails receipts. Developers have no control over that. Apple has some requirements for user information and consent with respect to purchases, but I'm not aware of any rules against developers going beyond the bare minimum.

That's too much of an open-ended question. Just pick one of the 5000 methods to accomplish this. Or perhaps recognize the inherent constraints of the platform and re-think how you display data to be more readable and useful on a small-screen platform.

When Apple, or anyone else, publishes source code on the internet, it is automatically copyrighted. Sometimes that copyrighted content includes an open source license. If so, then you can then use that code under the terms of that license. In theory, said license could say anything. But they typically conform to one of a number of standard open source licenses. Usually, you can continue to use and re-distribute the source even if the original content is removed. Just make sure to confirm that with the license itself. Apple's licenses are typically very unobtrusive. But licenses from other sources can be very restrictive. Unfortunately, Apple is well-known for deleting documentation, videos, and especially sample code. If they publish anything during this week's WWDC that seems like it might be useful, download and archive it. Never assume that anything Apple publishes will be available forever.

Never reply via comment. Your reply most likely won't be noticed. And there is no point in asking questions about new features a few hours before WWDC kicks off.

There is some "code" associated with that video. If you want the SceneKit original, you might try the archives. I see examples about a voxelpanda, a badger, and two foxes.

I think you misunderstood. This is most definitely not the forum for your users or testers. As an individual developer, it's important to remember that you're not Apple. Nor are you any other company with employees and a user experience budget. If you want people to test your app and give you feedback, you'll have to go looking for them. For many developers, the closest thing to real-world, end-user testing that they ever get is App Review.

Please don't use the Comment feature here in the forums. It's very annoying. Don't worry about those kinds of security issues. If your app reaches any level of popularity, then yes, it will absolutely be hacked. But at that point, you should consider the hackers to be an unpaid marketing team. Then, if your app continues to be successful enough so that the hackers are a noticeable detriment to your income, you'll have the resources to improve security and lock it down.

Try this instead: Task { await withCheckedContinuation { continuation in NSAnimationContext.runAnimationGroup { [self] context in context.duration = animated ? 0.5 : 0 clipView.animator().setBoundsOrigin(p) } completionHandler: { continuation.resume() } } endIgnoreFrameChangeEvents() }

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.

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.

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.

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.

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.

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.

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.