A Summary of the WWDC25 Group Lab

After my post, I found NSPopUpButton (or NSButton) has a private API named semanticContext for this purpose. Though, I can’t use it since my app is distributed in the App Store... cf. https://stackoverflow.com/questions/79593493/how-to-achieve-grouped-form-styled-controls-using-appkit/79607626#79607626

It does seem to be a permissions issue. If I revert back to putting the service in /Library/LaunchAgents and call SMAppService.agent(plistName: com.xpc.example.agent.plist) as demonstrated I can establish the XPC session and the code works as intended. That makes my claims of brokenness thoroughly, regretably invalid. It works, it's just not a complete example. Once I change the Copy File phase to throw the build product into /Library/LaunchDaemons and call SMAppService.daemon(plistName: com.xpc.example.agent.plist)instead (including passing the.private` flag when establishing the session), all the trouble begins. I manually did a chmod 600 and chown root on the service binary and the plist but launchd doesn't like that any better. I'm completely ruling out any .plist errors since I have not changed a single thing in that file and the same exact file works as a LaunchAgent. If I try to register the (root owned and non-group/world readable) plist manually then this happens: % sudo launchctl load /Appl

iOS 26 Navigation Title Not Displaying - Solution Problem Description After updating to iOS 26 beta, navigation titles stopped displaying in some of our SwiftUI views, while others continued to work. The affected views showed no navigation bar - the title, large title display mode, and toolbar items were not visible. This behavior is different from iOS 18, where the same code displays navigation titles as expected. Affected Configuration iOS Version: iOS 26 beta (all current betas through beta 7) SwiftUI: NavigationStack with .navigationTitle() and .navigationBarTitleDisplayMode(.large) Specific Pattern: Views where ScrollView or Form is the direct child of the view body The Change in Behavior In iOS 26, when a view's body directly returns a ScrollView or Form, the navigation title doesn't appear. Here's an example of code that displays the navigation title in iOS 18 but not in iOS 26: struct DashboardView: View { var body: some View { ScrollView { LazyVStack { // Your content here } } .navigationTitle(Dashbo

I’m presuming you’re targeting iOS or one of its child platforms here. The story is different on macOS. [quote='800040021, tverroman, /thread/800040, /profile/tverroman'] 1- What entitlements do we need? Do we need additional entitlements except com.apple.developer.networkingextension and com.apple.managed.vpn.shared? [/quote] Neither of those are valid entitlement names O-: When building an app with an NE provider, you need the com.apple.developer.networking.networkextension entitlement (note that you have the wrong spelling). This is restricted but not managed. Any developer can use it. To support managed configuration, you need access to the com.apple.managed.vpn.shared keychain access group. [quote='800040021, tverroman, /thread/800040, /profile/tverroman'] 2- What is the process to [access the] com.apple.managed.vpn.shared [keychain access group]]? [/quote] See #9 in Network Extension Framework Entitlements. [quote='800040021, tverroman, /thread/800040, /profile/tverroman'] 3- Is ADP …

It’s better to reply as a reply, rather than in the comments; see Quinn’s Top Ten DevForums Tips for this and other titbits. I am using macOS style that starts with Team ID OK. The Xcode App Group editor is not fully up to speed when it comes to macOS-style app group IDs. The screen shot of your provisioning profile shows the it’s correctly authorising you to use any group matching 2V________.*. And the App Groups editor is showing that you claim two of those groups. That’s all good. Note Regarding the group.com._.MySecurtiyAppGroup, it’s presence isn’t a problem. You’re not claiming access to that group, because the checkbox next it in the App Groups editor isn’t checked. And it’s fine for the profile to authorise you to use groups that you don’t then claim. I suspect that the red indicates that the app group ID you’re claiming isn’t literally in the app group ID listed in the profile. With iOS-style app groups

Right. System credentials go into a keychain access group that you don’t have access to. That’s why Safari and SFSafariViewController work, but your code fails. This has been a problems for a long time [1] but we finally have a solution, namely, the ManagedApp framework. This allows your app to receive credentials from your MDM system securely. AFAIK there’s no integration between this and SCEP, so you’d need to update your server to accept these client identities in addition to the SCEP ones. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] Check out the publication date on QA1745 Making Certificates and Keys Available To Your App!

Adding another App Groups image showing the grayed out group I do not remember adding. Clicking on the (i) in the developer provisioning profile also says there are 3 groups.

Turn off Blur for the group fixed this issue and was able to submit app for review. It is not the best but at least is a workaround.