A Summary of the WWDC25 Group Lab

We also face this issue. We are using AVAudioEngine for audio playback and manually control MPNowPlayingInfoCenter. We use AVPlayer for some silent background videos in app but when doing so the video player controls the playbackState with no way to opt-out. After filing a DTS, feedback and lab I am fairly sure there is no solution for this currently unfortunately. I filed FB9837867 and am crossing my fingers for some progress. Our current work-around which is not ideal is to set MPNowPlayingInfoCenter.default().nowPlayingInfo = nil whenever we pause the audio playback. This seems to somewhat work but also has some other not great side-effects. @Rodrigue2g Did you find any better solutions since posting this? I would encourage you to file feedback and mention FB9837867 as well!

Would it be possible to disable or hide the “Leave” button in the system screen? No. You can certainly file an enhancement request asking for use to provide/tweak what we show here, but the system is always going to provide some way for the user to directly stop the PushToTalk session. That's because one of the primary goals of the PushToTalk framework was providing user level control over this. I only receive the APNs push notification “type: voip-ptt“ once per active channel. My forum post here goes into this in depth, but the quick summary is that you shouldn't think of the PushToTalk framework's channel as the same thing as your apps. The PushToTalk framework's channel is simply it's connection to your app. There will ONLY ever be one of them and you should not be creating/leaving/joining that channel dynamically. You join it when your PTT session starts and you don't leave it until you session is done. Again, see my other forum post for more details on that means in practice. My app is running i

They talk about this in the WWDC25 video, Meet the Foundation Models framework starting at 19:55 in the presentation.

Can somebody point me to documentation on how to send this type of push notification for incomingServiceUpdatePush or give me an example payload? No, but please do file a bug about this and post the bug number back here, as this really should be in the public documentation. Having said that, you are in fact the second person who's ever asked about this (the first being the team who asked us to add this feature). give me an example payload? Here is the quick summary: They are sent using the PTT token. The push topic is pushtotalk. The push payload includes the key ptt-push-type with a value of service-update. Here is an example using curl: curl -v -d ‘{“aps”:{“ptt-push-type”:”service-update”,…}}’ -H apns-push-type: pushtotalk -H apns-topic: .voip-ptt” -H apns-priority: 10 -H apns-expiration: 0 --http2 --cert .pem https://api.sandbox.push.apple.com/3/device/ Keep in mind that, as the documentation notes, service updates are budgeted* and delivery will stop if/when the app exceeds it's budge. Us

I think this is an unwanted consequence of two separate things: Modern versions of Xcode use the network for interacting with the device. When you save an NE content filter configuration, the system tears all network connections so that the filter can see them [1]. There’s a long-standing request from developers for a way to control that second behaviour (FB13516440), but that’s not happened yet. In the absence of that, I don’t see a great way around this problem. It would absolutely make sense for you to file a bug about this issue. If you do that, please post your bug number, just for the record. If you’re doing this a lot it might make sense for you to build some infrastructure to simplify your debugging flow. You could, for example, have the filter read its configuration from a shared app group, and then use another app to set that. That would avoid the need for a change to the vendor configuration setup, and hence this issue. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @

Hello! If you're using the Quick Look PreviewApplication API on visionOS 2+ to present spatial photos, then when the viewer switches to immersive presentation, Quick Look will hide other apps to focus the viewer on just the photo they are viewing immersively. As an alternative, in visionOS 26 you can also use the new ImagePresentationComponent from RealityKit, which enables you to present 2D photos, spatial photos, and spatial scenes in windowed and immersive spaces yourself. This gives you more control over what other content remains visible when presenting the spatial photo immersively. Check out the Immersive media section of What's new in RealityKit from WWDC25 for more information. There's also a new Presenting images in RealityKit sample code project to help you get started.

Hello! visionOS 26 introduces ImagePresentationComponent, which enables you to present 2D photos, spatial photos, and spatial scenes in windowed and immersive spaces with RealityKit. Check out the Immersive media section of What's new in RealityKit from WWDC25 for more information. There's also a new Presenting images in RealityKit sample code project to help you get started.

As part of the 6/12/25 SwiftUI Group lab, Curt and Taylor spoke to this specifically related to use of color in liquid glass SwiftUI views and that use of color should be limited. However, they didn’t speak to how to put color back into List View outline disclosure carets that aren’t there in new iOS/iPad OS 26. I would still like to know if I can add color back into the carets. Here was my group lab question that was discussed: “I’ve noticed with the new design language, SwiftUI views appear to not use color as much. Example, color modifiers for List View items like carets. Is this intended and can developers introduce color back into SwiftUI view elements, if desired, like in iOS/iPadOS 18?”

[quote='841755022, DTS Engineer, /thread/786366?answerId=841755022#841755022'] com.apple.security.application-groups is a code signing entitlement, not an Info.plist key [/quote] I was confused when I read something suggesting it needed to be included in each Info.plist. My entitlements.mas.plist already includes this key with the proper value and format. That should be the extent of what is needed for group permissions from what I can find. After more research, I'm suspecting the permission issue might be a broader issue with Electron itself. There were permission errors when initially installing that package and I'm wondering if something wasn't resolved there. I also discovered the TestFlight version was somehow launching from the project's root and not the sandboxed Applications folder at one point ('fixed' by running under another user account). Planning to try a full reinstall.

I took the opportunity to ask about this in a WWDC lab and we found a solution at least for edited items: NSPredicate(format: not adjustmentFormatIdentifier == nil) They also confirmed that there is no comprehensive list of available predicates documented anywhere and encouraged me to submit some feedback to request this.