Post

Replies

Boosts

Views

Activity

Reply to Invalid code signing entitlements with app group on macOS
To whom it may concern and help: Summary: If you have macOS Apps and use App Groups and want to distribute to the App Store, do yourself a favour and upgrade your macOS to Sequoia and Xcode to at least 16.3. Detail: I had no issues with app groups for macOS apps until after mid Feb 25. I used Xcode 15.2 on a Ventura iMac. Then, as per posts above, it all failed upon distribution. I also saw two AppGroup capabilities in Signing&Capability. I tried everything I read here and more. Registered the app group (although it is not necessary for a macOS app), included in Build Settings the 'Register App Group' trick from Eskimo (but it is for iOS App Groups), tried to monitor what is going on with my provisioning profile (but dump on exported app does not work as macOS apps do not embed a provisioning profile I think), deleted all provisioning profiles, created my own manually etc etc. Nothing worked. Upgrading to Sequoia and Xcode 16.3 does it without any pain: no registration of the App Group necessary, only 1 App Group in Signing and Capabilities, no configuration of AppGroups in AppID identifier necessary (as this would be for iOS App Groups) - only ticking the box for the AppGroup Capability.
Topic: Code Signing SubTopic: Entitlements Tags:
Apr ’25
Reply to Invalid code signing entitlements with app group on macOS
Help please. I have two macOS apps, that both share an App Group to exchange information. I use Xcode 15.2, Ventura 13.6.1 Until mid Feb 25, all was working fine, but now I get the same error message upon distribution attempt as many above: Provisioning profile failed Qualification; Profile doesn't support App Groups. I also now have two capabilities, both called App Groups in my Signing&Capability section; One lists my App Group, starting with the team name as it is a macOS app and another capability that just states: Application Groups entitlement may require additional configuration. With an arrow that points to my entitlement file that contains the macOS app group name. If I try to delete the second one, that was not there before, both App Group Capabilities are deleted, together with the corresponding entitlement. In my developer account, the app IDs have the App Group box selected but I did not further 'configure', including registration, as this is a macOS app and any name other than starting with group (for iOS app groups) is not accepted. I deleted the provisioning profiles in MobileDevice folder, but to no avail (no UserData folder in Ventura I think) Am I missing something? I tried to follow all the comments within this thread. The only item I failed with was to dump the actual provisioning profile. I selected Direct Distribution for the archived project and then exported it. It is exported as an app, not an installer file And when trying to dump the app, I get the error message that the embedded provisioning profile is not found. So what used to be a formality procedure, has now taken a day of my life ;-) and I am still no wiser. Any help appreciated!
Topic: Code Signing SubTopic: Entitlements Tags:
Mar ’25
Reply to Invalid code signing entitlements with app group on macOS
To whom it may concern and help: Summary: If you have macOS Apps and use App Groups and want to distribute to the App Store, do yourself a favour and upgrade your macOS to Sequoia and Xcode to at least 16.3. Detail: I had no issues with app groups for macOS apps until after mid Feb 25. I used Xcode 15.2 on a Ventura iMac. Then, as per posts above, it all failed upon distribution. I also saw two AppGroup capabilities in Signing&Capability. I tried everything I read here and more. Registered the app group (although it is not necessary for a macOS app), included in Build Settings the 'Register App Group' trick from Eskimo (but it is for iOS App Groups), tried to monitor what is going on with my provisioning profile (but dump on exported app does not work as macOS apps do not embed a provisioning profile I think), deleted all provisioning profiles, created my own manually etc etc. Nothing worked. Upgrading to Sequoia and Xcode 16.3 does it without any pain: no registration of the App Group necessary, only 1 App Group in Signing and Capabilities, no configuration of AppGroups in AppID identifier necessary (as this would be for iOS App Groups) - only ticking the box for the AppGroup Capability.
Topic: Code Signing SubTopic: Entitlements Tags:
Replies
Boosts
Views
Activity
Apr ’25
Reply to Invalid code signing entitlements with app group on macOS
Help please. I have two macOS apps, that both share an App Group to exchange information. I use Xcode 15.2, Ventura 13.6.1 Until mid Feb 25, all was working fine, but now I get the same error message upon distribution attempt as many above: Provisioning profile failed Qualification; Profile doesn't support App Groups. I also now have two capabilities, both called App Groups in my Signing&Capability section; One lists my App Group, starting with the team name as it is a macOS app and another capability that just states: Application Groups entitlement may require additional configuration. With an arrow that points to my entitlement file that contains the macOS app group name. If I try to delete the second one, that was not there before, both App Group Capabilities are deleted, together with the corresponding entitlement. In my developer account, the app IDs have the App Group box selected but I did not further 'configure', including registration, as this is a macOS app and any name other than starting with group (for iOS app groups) is not accepted. I deleted the provisioning profiles in MobileDevice folder, but to no avail (no UserData folder in Ventura I think) Am I missing something? I tried to follow all the comments within this thread. The only item I failed with was to dump the actual provisioning profile. I selected Direct Distribution for the archived project and then exported it. It is exported as an app, not an installer file And when trying to dump the app, I get the error message that the embedded provisioning profile is not found. So what used to be a formality procedure, has now taken a day of my life ;-) and I am still no wiser. Any help appreciated!
Topic: Code Signing SubTopic: Entitlements Tags:
Replies
Boosts
Views
Activity
Mar ’25