A Summary of the WWDC25 Group Lab

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() }

Hi Quinn “The Eskimo!” (Apple DTS), Thanks for your follow-up. We’ve submitted the complete diagnostic data and supporting logs through Feedback Assistant. Feedback ID: FB20868550 📂 Uploaded files include: Full sysdiagnose from iPhone 17 (iOS 26.0.1) Device-side BLE log showing PHY update and disconnect nRF Sniffer trace (2M PHY update failure) Comparison trace from iPhone 16 (iOS 25) — fallback works correctly Readme with timestamps and reproduction steps 🧩 Issue summary When connecting to our BLE device, iPhone 17 (iOS 26.x) first connects using 1M PHY, then attempts to update to 2M PHY. If the 2M update fails, the phone immediately disconnects instead of falling back to 1M — unlike other iPhones which recover gracefully. This issue causes immediate disconnection and affects compatibility with over one million deployed devices. Please confirm if the diagnostic files under FB20868550 are accessible and sufficient for analysis, or let us know if any additional logs or captures would be helpful. Tha

SceneKit is soft-deprecated and we suggest using RealityKit if you are thinking about making new games. To learn how to bring your existing SceneKit projects to RealityKit, see Bringing your SceneKit projects to RealityKit. This article and sample code project are associated with the WWDC25 session Bring your SceneKit projects to RealityKit. If you see any issues bringing over your projects to RealityKit or see any missing features, please file a request via Feedback Assistant.

Thanks for the detailed response. To clarify and add some details about my testing setup and observations: Verification that the extension isn’t being triggered: I’ve confirmed that the Notification Service Extension (NSE) is not being invoked at all and not just failing to modify the content with the following pointers: The didReceive(_:withContentHandler:) and serviceExtensionTimeWillExpire() methods never log or execute (I’ve added multiple test print/log statements and file-based logs for confirmation). The extension process itself does not appear in Console.app or in the process list. On iOS, using the exact same payload and code, I can see clear logs from the extension when it runs — so the extension logic and payload are validated there. Console logs checked: I’ve filtered the macOS Console for both the main app bundle ID and the extension’s bundle ID. There are no messages indicating the NSE being launched, terminated, or crashing. The system only logs the standard “Received remote notification” messa