A Summary of the WWDC25 Group Lab

It appears to be correctly signed. Automatically manage signing is checked, my standard team is set. With those settings, as soon as I assign an app group in Xcode 26.1, it changes to an Xcode managed provisioning profile and my valid Apple Development certificate and does not let me change them. I also checked the build with codesign -dv --verbose=4 and in ~/Library/Developer/Xcode/UserData/Provisioning Profiles to verify and that the profiles update, e.g., when I change the Info.plist. I also tried setting up a fresh sample project from the standard multiplatform SwiftUI app template in Xcode and did not change anything in Signing & Capabilities except setting the app group for the app and download extension. Same minimal app just calling AssetPackManager.shared.assetPack(withID:), same result: on iOS it works, on macOS the URL override is not permitted.

Hello @sadaotokuyama, thank you for your question! I think there's some confusion over what is required to show immersive video so hopefully I can clarify in this post. Based on the description of what you want to do, I recommend searching for the term APMP or Apple Projected Media Profile. Check out the video Learn about the Apple Projected Media Profile from WWDC25 for more information. Specifically, there is a graphic shown at about 1 minute and 20 seconds that shows all the different formats side by side. For additional resources check out Explore video experiences for visionOS which goes into all the different ways of presenting media on Vision Pro, and also Support immersive video playback in visionOS apps. Apple Immersive Video is a high-end immersive video format on Vision Pro. To shoot content for this format you'll need a piece of equipment like Blackmagic's URSA Cine Immersive camera. However, APMP video is much more accessible, and can be shot on a wider variety of cameras, because APMP i

Have you asked Gemini or ChatGPT about this case? When it comes to Swift Concurrency, they are quite good at it. Concerning your issue, Gemini reports to me several issues with the following last comment. In summary, the most critical issue is the unreliable view hierarchy traversal using view.superview?.superview. You should refactor the ViewExtractor to reliably pass the host UIView back to the modifier.

Could this be due to the fact that my subscriptions are still Waiting for Review (not yet “Ready for Sale”)? If yes, is there any way for the App Review or developer testing environment to see them before they are approved? No. Testing In-App Purchases in the sandbox doesn't require prior approval from Apple. Reviewing your In-App Purchases doesn't require prior approval from Apple. The Waiting for Review status indicates you have submitted your In-App Purchase to be reviewed by Apple. You can continue testing while they are in review. Products: Auto-renewable subscriptions Can you confirm you set up price and added localizations for your subscriptions and their subscription group in App Store Connect?

You can quite easily see NSScrollView jitter/stall if you open a Finder window -> Icon view -> Use Groups -> yes. Make sure the folder you are viewing has a few collapsable sections. Collapse some of them. Then start vertically scrolling top to bottom. Scrolling will get interrupted often when the cursor moves over the collapsed sections. The scrollbar will freeze visible until you click somewhere and then the scrolling animation will start. You might think the horizontal scrolling of the collapsed section is colliding with the vertical scrolling and that that is causing the stutter but that's not what's happening. In my testing I can just stick a subview partially outside the bounds of the document view (but not increase the width of the document view so horizontal scrolling is not enabled) and the same stutter occurs. I went back to macOS Monterey and tried to reproduce but could not. Not sure when this bug came about. But adjusting the scroll point in a -scrollWheel: override without call

Hi, I did not try this on iPad yet will test this over the weekend. In the meantime here is the bug number: FB21023986 Btw I will be in London's developer lab on 18th of December maybe something I could address/show there as well.

I just discovered that PKDrawing now lists the same method .draw(in: , frame:) also as asynchronous drawing code. This will only work as of iOS 26 and up. I wonder if this is going to be the way forward for CGContext drawing code, and if so, how should we treat the block drawing in an async closure. Take this example from WWDC25 Meet Paperkit: // Set up CGContext to render thumbnail in let thumbnailSize = CGSize(width: 200, height: 200) let context = makeCGContext(size: thumbnailSize) context.setFillColor(gray: 1, alpha: 1) context.fill(renderer.format.bounds) // Render the PaperKit markup await markupModel.draw(in: context, frame: CGRect(origin: .zero, size: thumbnailSize)) thumbnail = context.makeImage() }