A Summary of the WWDC25 Group Lab

Hi, In my app, I have an option to remove a contact from a contact group (using the Contacts framework), and it's been working fine till recently users of the macOS version reported that it's not working. I have been using the CNSaveRequest removeMember(contact, from: group) API. The same API works fine on iOS. I'm not sure when it started but it seems to be affecting macOS14.6 as well as 15.1. I was able to reproduce it in a small test project as well, and have the same experience (the API works on iOS but not on macOS), so it definitely seems like a problem with the framework. Can someone confirm this, and/or suggest a workaround? Here's the code I run to test it out ...a simple SwiftUI view that has 4 buttons: Create contact and group Add contact to group Remove contact from group (optional) cleanup by deleting contact and group It's the 3rd step that seems to fail on macOS, but works fine on iOS. Here's the code to test it out: struct ContentView: View

I want to create logical groups inside my Finder Extension context Menu.http://stackoverflow.com/questions/42537343/how-to-create-logical-groups-inside-a-context-menu-mac-os/42541596?noredirect=1#comment72302097_42541596The discussion on the aforementioned StackOverflow thread suggests that the[NSMenuItem separatorItem]behaves inconsistently for me and another user. While for me it creates a blank space, for the other user it draws a horizontal line between the menu items ( This is what i want to achieve).

I have an app that's been out for awhile and uses the Keychain to store a token. Now, I'm adding an extension to my app, and so I'm using the methods described in the App Extension Best Practices sesion from 2015 to share a secret between my app and my extension using an access group.My question is about the automatic search behavior for the query API. It's said in the session that update/delete/matching all do the right thing with accessible keychains. What keychains are supposed to be accessible to the extension? What I'm finding is that for existing app users (people who had saved the secret before I was using access groups), my extension has access to the keychain item despite it not having an access group. What I anticipated was that that wouldn't work, and I'd have to do some kind of migration step to move my non-access group item into an acess group one. But it looks like I don't have to do that, at least when I'm debugging with Xcode. Am I missing something here or

I am developing a Mac app that makes use of App Scripting. The is Sandboxed and thus needs the proper entitlements in order to get permissions to send AppleScript events to other apps. I have gotten this working properly for apps (like Mail and spotify) which specify access-group identifiers like this:<access-group identifier=com.apple.mail.compose access=rw/> <access-group identifier=com.spotify.playback/>However, a few other of the Apple made apps (like Xcode) specify their identifiers like this:<access-group identifier=*/>I have tried to configure my entitlement file like this:<key>com.apple.security.scripting-targets</key> <dict> <key>com.apple.dt.Xcode</key> <array> <string>*</string> </array> </dict>, but when doing this it does not work and I get this error message in the console:AppleEvents/sandbox: Returning errAEPrivilegeError/-10004 and denying dispatch of event xcod/buld from process '

Overall love this version, but am seeing 2 issues with this new version: 1) Groups I've created in Contacts are no longer visible, and the option to create Groups also is not available. When I switch back to the old Outlook (it's a toggle at the top of the screen), Groups are back and usable 2). I have multiple O365 accounts (3) that I use in Outlook, one of the accounts does not seem to function properly when I switch to the new version. Would welcome input on both

Do App Groups still work on Watch OS 2 as a mechanism for sharing files between the watch and iPhone?(Since WatchKit extension will now reside on the watch instead of the iPhone)What changes to we need to make to the existing codebase?

I recently changed my developer account from account A to account B. I have successfully transferred my applications. With transfer of applications my app group was not migrated. Question - Can I deleted the app group from account A and recreate it in account B with the exact same identifier. If means does it affects the live users. Which means does the live user can able to use our application without any data loss(Logout)

Prior to Sequoia, Mac Catalyst Apps worked fine when using group folders that started with group. They now get an alert that the Mac Catalyst app is trying to access data from other applications. This may also impact some SwiftUI developers. According to this the documentation for the App Group Entitlements entitlement, on macOS we should begin use the Team Identifier instead of group. Should Mac Catalyst follow the macOS or iOS rules for com.apple.security.application-groups? If they should need to follow the macOS rules now, that creates several issues for developers. We would now need separate build targets to pick up the different Entitlements files. More distressing is that we would need to do some kind of migration process to get our files to the new location. There wouldn't be a transparent way to do so where the user wasn't warned about the application accessing files that don't belong to it. Any clarification on what Mac Catalyst developers should be doing

I know it was not possible previously, but wonder have things changed to support transfer of apps with this condition: Sandboxed Group Container You can only transfer sandboxed apps that are not sharing a group container. Our old company is having some issues and cannot continue, and would like to transfer to another company without doing the binary reassignment process which loses all the reviews. Thank you!