Thanks for confirming that. I would expect this to work. When you use an iOS-style app group ID in a Mac Catalyst app, Xcode generates a provisioning profile to authorise that use. So this use falls under case D in App Groups: macOS vs iOS: Fight!. Consider this tiny test app I just created: % codesign -d --entitlements - Debug-maccatalyst/Test766580.app Executable=/Users/quinn/Library/Developer/Xcode/DerivedData/Test766580-beavevigoaauqrfhkfssttblupau/Build/Products/Debug-maccatalyst/Test766580.app/Contents/MacOS/Test766580 [Dict] … [Key] com.apple.security.application-groups [Value] [Array] [String] group.eskimo1.test [Key] com.apple.security.get-task-allow [Value] [Bool] true … % security cms -D -i Debug-maccatalyst/Test766580.app/Contents/embedded.provisionprofile | plutil -p - { … Entitlements => { … com.apple.security.application-groups => [ 0 => group.eskimo1.test ] … } … } Note the presence of com.apple.security.get-task-allow, showing that this is a development build. And that group
Topic:
Code Signing
SubTopic:
Entitlements
Tags: