A Summary of the WWDC25 Group Lab

Thank you @illidan80. We found the underlying cause. The framework currently only supports adapters whose identifiers match the regex /fmadapter-w+-w+/. Here, your adapter name foundation-lab contains a hyphen, which tripped our name validation logic. If you update the adapter name in the toolkit to foundation_lab, that should resolve the issue. To test this quickly without re-exporting the adapter, you can manually edit the adapterIdentifier entry in the metadata.json file to fmadapter-foundation_lab-9799725. Thank you for reporting the issue and the follow-up debugging steps. We will use your feedback FB19237327 to track an improvement to the adapter training toolkit to perform this validation at adapter export time. Please don't hesitate to reach out again if you need more help with custom adapters!

App groups have been evolving a lot recently, primarily to bring the macOS and iOS stories into alignment. See App Groups: macOS vs iOS: Working Towards Harmony for all the backstory. Your app group ID, $(TeamIdentifierPrefix)group.com.example.testapp.mobile, is weird. It seems be a macOS-style ID, with the Team ID prefix, but then it also kinda uses the iOS-style format. I recommend that you use one or the other. Actually, I’ll take that one step further: I recommend that you you use an iOS-style app group ID unless you have a really good reason to stick with a macOS-style one [1]. As to what’s going on here, it’s hard to say. I tried looking up the state of com.example.testapp.mobile but AFAICT that’s not your real bundle ID, but rather a placeholder you used for this post. What version of Xcode are you using? If you’re using anything older than Xcode 16.4, I recommend that you upgrade to that. Xcode 16.4 is aware of this app group harmonisation effort. And once

And to build on my colleagues answer above, the code of interest in that project is in TrailShortcuts.swift: AppShortcut(intent: GetTrailInfo(), phrases: [ Get (.$trail) conditions with (.applicationName), Get conditions on (.$trail) with (.applicationName) ], shortTitle: Get Conditions, systemImageName: cloud.rainbow.half, parameterPresentation: ParameterPresentation( for: .$trail, summary: Summary(Get (.$trail) conditions), optionsCollections: { OptionsCollection(TrailEntityQuery(), title: Favorite Trails, systemImageName: cloud.rainbow.half) } )) — Ed Ford,  DTS Engineer

Thanks a lot for your response. Sorry, I have not enoughly described my goal. I work in a HCI research lab, so I will probably try to do things that are not conventionnal. My full idea is to stream another XR scene on top of a current RealityKit scene. For that purpose, I try to get a realtime stream of the other scene, rendered side-by-side, that I apply on a plane with a material that render for each eye anchored to the head send to the other scene inputs (head pose, hands, etc...) to keep in sync the rendering This way, even if I anchor the texture to the head, It will be updated depending on head pose like a normal xr scene, and will just act as a scene layer. Ideally, I would also put depth into the stream texture to be also able to render at the right depth and no more do a scene layer but kind of scene fusion. In some way, I'll try to reproduce at a higher level some kind of compositor between multiple immersive scenes. I currently think that I can only do that with Compositor Services without

After testing in our tech lab with all devices updated to iOS/iPadOS 18.6, I’m seeing improved behavior overall, but some inconsistencies remain, particularly with older hardware. On iPhone SE (18.6), the issue does not reproduce. Local network access from the extension works as expected. On iPad 10th gen (18.6), the issue is no longer observed. Notably, this device did occasionally fail on 18.5. On iPad 7th gen (18.6), behavior remains inconsistent. The extension is sometimes able to send local network traffic, but in other cases, it fails with the same “Local network prohibited” error. Success seems more likely after switching Wi-Fi networks or if the main app has already made a successful local connection beforehand, but this is not reliable or predictable. So while iPadOS 18.6 clearly improves the situation, it appears that residual issues may still affect older devices. I’ll be extending testing to 8th and 9th gen iPads on Monday and will share any additional findings. Let me know if there are a

Is there a modifier to make section headers non-sticky? You can use the automatic .listStyle(.automatic) or opt for a lazy stack instead and apply your decorators. For examples, refer to Grouping data with lazy stack views. .listStyle(.automatic) results in in .insetGrouped, so that's a different look. I tried the LazyVStack approach and this worked well for a screen that was pretty custom-styled anyway. Side note: LazyVStack made me a little upset by applying the spacing not only between rows, but also after the section header; requiring dancing around with the spacing and paddings to get the correct look; I wished for a separation of spacing between sections, spacing between rows and spacing between [section header/rows/section footer]. But I'm wondering if this is a well-rounded approach for Views that just want a plain styled data list. It's certainly more feasible with the delicate separators-going-all-the-way-through-to-the-edge-of-the-screen gone in iOS 26, but still, custom-rebuilding all the

The API highlighted by @RickMaddy is one of the only choices, in addition to the newer excludedActivitySectionTypes property. It's worth though taking a step back and looking at your core premises: We are currently developing an enterprise iOS application and are in the process of implementing Data Leakage Protection (DLP) features. In broad terms, an app generally does not have the right level of visibility to understand the mix of user intention and corporate data policies. An app is not an island, and may be only one of several apps to get specific work tasks done. That's why the right thing here is that the device needs to be managed by the enterprise through MDM, so there's a higher level view of what the enterprise intends to allow and disallow through its chosen policies. There's a chain of trust to this — if an enterprise doesn't trust the device by managing it at the device level, then why should it trust a potentially unknown device with an unmanaged app with its sensitive enterprise data? There is

Is there a modifier to make section headers non-sticky? You can use the automatic listStyle .listStyle(.automatic) or opt for a lazy stack instead and apply your decorators. For examples, refer to Grouping data with lazy stack views. Is there a way to get a blurry material behind the section headers when they are sticking to the top bar? You can provide a background for your section header. However you can't provide a material for the scrollEdgeEffectStyle apart from either hard or soft ScrollEdgeEffectStyle. Can you give safeAreaBar(edge:alignment:spacing:content:) a try and disable the scroll edge effect using scrollEdgeEffectHidden. That would allow you provide a view as a custom bar.