A Summary of the WWDC25 Group Lab

Hi @377632523@qq.com, I'm unable to reproduce the issue, as reported, in my own Xcode project. Because the provided example above will not build successfully due to missing types, I replaced your implementation with the following: import SwiftUI struct PhotosMainView: View { @State private var searchText: String = var body: some View { TabView { Tab(Library, systemImage: photo.on.rectangle) { NavigationStack { scrollView(colors: [.red, .orange, .yellow]) .navigationTitle(Library) } } Tab(Albums, systemImage: square.grid.2x2) { NavigationStack { scrollView(colors: [.yellow, .green, .teal]) .navigationTitle(Albums) } } Tab(Search, systemImage: magnifyingglass, role: .search) { NavigationStack { scrollView(colors: [.blue, .purple, .pink]) .navigationTitle(Search) .searchable(text: $searchText) } } } .tabBarMinimizeBehavior(.onScrollUp) .tabViewStyle(.sidebarAdaptable) .tabViewBottomAccessory { TimelineAccessoryView() } } // Trivial helper view to visualize scrolling. @ViewBuilder func scrollView(colors: [Color]

Hi we are having the same problem, cannot test the app on TestFlight at all. Surreal All devices, all groups :(

Thanks a lot for your super-fast advice! My results have increased quality. I only need a bit more of information about when is a best practique incorporate a description for a Guided attribute. @Generable struct SearchSuggestions { @Guide(description: A list of suggested search terms, .count(4)) var searchTerms: [String] } Listening the WWDC25 session Deep dive into Foundation Generation Models from min 9:00 to 9:15: Multiline Foundation Models will even automatically include details about your Generable type in the prompt, in a specific format that the model has been trained on. You don’t have to tell it about what fields your Generable type has BlockQuote I interpret that with an auto-descriptive name to the attribute like SearchSuggestions write a description is overwork because the model already may infer what must be the content. Am I right? If my state is true, go deeper and learn what must be set in the description. Some examples would be the best to set clearly best practiques 😀

Hi Kevin, Thank you for the detailed response. Here is a summary of our tests based on the solutions you proposed: Regarding the userclient-access Entitlement: We discovered a human error in our initial entitlement request (we had entered the wrong Bundle ID). We have submitted a new, corrected request with the proper DEXT Bundle ID and are currently awaiting its approval. Regarding the Temporary Solutions: To continue development while waiting, we tried your other suggestions, but are still blocked. App Sandbox: We confirm that com.apple.security.app-sandbox is set to false in our app's entitlements. This alone did not solve the issue. IOKit User Client Class Temporary Exception: We implemented your third suggestion precisely. Our app's .entitlements file for this test was configured exactly as follows: com.apple.security.temporary-exception.iokit-user-client-class IOUserUserClient com.apple.security.app-sandbox com.apple.developer.system-extension.install com.apple.security.get-task-allow

May seem like a dumb question but I'm somewhat overwhelmed by the amount of information and all the terms and conditions as it relates to this topic. There are several threads about cross platform issues, etc. as it relates to app groups but that is not my situation. Not too long ago I asked a similar question about a different app (not new but an update) and I just stuck with the group prefix on that one but I'd like to know what the recommendation is for a new Mac app. So I have this simple situation: I have a new Mac app. Two versions: Mac App Store (sandboxed) Non-Mac App Store (not sandboxed). They both use XPC service embedded in the app. XPC service + main app need an app group. Both non-MAS and MAS use app groups with their own XPC services (not with each other) I always used teamIdprefix.groupidentifier. So I configured and registered the group identifier for the outside the Mac App Store version because Xcode prompted me to. I'm using group. pref

Hi Smith, Thank you so much for your excellent suggestions. I've followed your advice and have some definitive results to share. Regarding your first suggestion (Inspecting the Provisioning Profile): You were absolutely right. I inspected the latest Xcode-managed .provisionprofile for my app (com.accusys.Acxxx.app) after a complete cleanup. The profile does not contain the correct value for the userclient-access entitlement. Here is what the profile's Entitlements dictionary contains: com.apple.developer.driverkit.userclient-access: com.accusys.Acxxx.app com.apple.application-identifier: K3TDMD9Y6B.com.accusys.Acxxx.app keychain-access-groups: K3TDMD9Y6B.* As you can see, the value for userclient-access is incorrectly set to the app's own bundle ID, not the DEXT's (com.accusys.Acxxx.driver). Regarding your second suggestion (Using allow-any-userclient-access): I also tried the alternative strategy you proposed, which is a setup we had already been testing. Here is the configuration: App Entitlements