“A Summary of the WWDC26 Group Lab”

We have a macOS app that has a Photos Extension, which shares documents with the app via an app group container. Historically we used to have an iOS-style group identifier (group.${TeamIdentifier}${groupName}), because we were lead by the web interface in the developer portal to believe this to be the right way to name groups. Later with the first macOS 15 betas last year there was a bug with the operating system warning users, our app would access data from different apps, but it was our own app group container directory. Therefore we added a macOS-style group identifier (${TeamIdentifier}${groupName}) and wrote a migration of documents to the new group container directory. So basically we need to have access to these two app group containers for the foreseeable future. Now with the introduction of iOS-style group identifiers for macOS, Xcode Cloud no longer archives our app for TestFlight or AppStore, because it complains: ITMS

I am using SharePlay and the Group Activities framework in my app and my usecase requires the number of participants, so I am trying to get it like this: _ = SharePlayManager.sharedInstance.groupSession?.$activeParticipants.sink(receiveValue: { participants in print(participants.count) }) But this always prints 0, am I doing something wrong? (groupSession is 100% not nil)

Hi all, I am trying to display the name of the group in the subtitle of the communication notification, like this: Here is my code: override func didReceive(_ request: UNNotificationRequest, withContentHandler contentHandler: @escaping (UNNotificationContent) -> Void) { self.contentHandler = contentHandler var personNameComponents = PersonNameComponents() personNameComponents.nickname = Test Person let avatar = INImage(url: URL(string: https:imageURL)!) let senderPerson = INPerson(personHandle: INPersonHandle(value: 1233211234, type: .unknown), nameComponents: personNameComponents, displayName: Test Person, image: avatar, contactIdentifier: nil, customIdentifier: nil, isMe: false, suggestionType: .none) let mePerson = INPerson( personHandle: INPersonHandle(value: 1233211232, type: .unknown), nameComponents: nil, displayName: nil, image: nil, contactIdentifier: nil, customIdentifier: nil, isMe: true, suggestionType: .none) let incomingMessagingIntent = INSendMessageIntent(recipients: [mePerson], ou

Certificate Details Certificate Name Expro International Group Ltd Certificate Type iOS Distribution Expiration Date 2029/02/11 Created By Thavaseelan Kudarsamy Enabled Capabilities iCloud, In-App Purchase, Personal VPN, Push Notifications App ID ESTSMobile (com.exprogroup.estsmobile) This profile is not installing.

Hello, I have multiple apps that i would like to login with apple login connected to same backend. I enabled sign in with apple on all and told them to group with primary app id which is one of them. I went and created 1 service id and key and used that on the backend to login the user. I can login fine on the primary app id but not on the grouped ones. Am I missing anything setup wise?

I am unable to add a Group to my app's TestFlight build. Steps: In App Store Connect, Go to TestFlight > Build # > Add Group (Group + button) Add 'Export Compliance Information' Click on 'Start Internal Testing' When following these steps, the entire screen reloads, however navigating back to the same screen shows that no Groups have been added to the build. A friend who is on the same account is able to follow these steps successfully. Is there something we should be checking to allow me to do this?

Howdy, My macOS application uses app groups, using an entitlement file similar to the one below. com.apple.security.application-groups $(TeamIdentifierPrefix)com.example.test This all works when using my local Xcode. However, when I push the job to our CI/CD server I get an error. error: Provisioning profile doesn't include the com.apple.security.application-groups entitlement. Profile qualification is using entitlement definitions that may be out of date. Connect to network to update. Searching around, namely macOS Unsatisfied entitlements com.apple.security.application-groups and System Extension app-group entitlement issue tells me that I do not need to have the app group contained within my provisioning profile, due to how macOS handles App Groups differently to iOS. Is there a way to tell xcodebuild on my CI box to ignore this and continue building?

Hello,I encounter the following problem with NSUserDefaults and app groups:I added a today extension to my main app and created an app group so that I can share data with the extension. I moved my user defaults to the app container by usingNSUserDefaults(suiteName: SharedConstants.appGroup)(where SharedConstants.appGroup is a constant from a dynamic framework). I instantiate the user defaults in the extension the same way. Note that I successfully created the app group in the developer portal and it displays as correct in both targets. I successfully share CoreData with the extension.My main app registers default values for all settings I store in the NSUserDefaults by reading a plist file from the app's main bundle like this:NSBundle.mainBundle().URLForResource(DefaultSettings, withExtension: plist)This worked with standardUserDefaults as expected and I did not change this due to the fact that the extension does not need to register default values (though there are fallbacks for the rare ca