Search Issue Tracker

By Design

Votes

0

Found in

2022.3.33f1

Issue ID

UUM-74143

Regression

No

[MacOS] Invalid Code Signing Entitlements errors appear when signing MacOS project for App Store

-

How to reproduce:
1. Download and open the attached project
2. Build the project for MacOS
3. Sign and upload the project to AppStore

Expected outcome: No errors appear
Actual outcome: "ITMS-90288: Invalid Code Signing Entitlements - The entitlements in your app bundle signature do not match the ones that are contained in the provisioning profile. According to the provisioning profile, the bundle contains a key value that is not allowed: '' for key 'com.apple.application-identifier' in 'SlashQuest.app/Contents/PlugIns/Rewired_MacOS.bundle
'ITMS-90286: Invalid Code Signing Entitlements - Your application bundle's signature contains code signing entitlements that are not supported on macOS. Specifically, value '' for key 'com.apple.application-identifier' in 'SlashQuest.app/Contents/PlugIns/Rewired_MacOS.bundle' is not supported. This value should be a string starting with your TEAMID, followed by a dot '.', followed by the bundle identifier." errors appear in the console window

Reproducible with: 2022.3.33f1, 2023.2.20f1, 6000.0.5f1

Note: This happens when trying to sign the .app manually using the codesign tool or generating a xcode project directly from unity using Auto Signing.
Note: Commands used for signing:
{noformat}# for every dylib in Frameworks
codesign --force --verify --verbose --timestamp --options runtime
--sign $CERT_DISTRIBUTION
--preserve-metadata=identifier,entitlements,flags
"$BUILD_PATH/AppName.app/Contents/Frameworks/*.dylib"
# for every bundle in PlugIns
codesign --force --verify --verbose --timestamp --options runtime
--sign $CERT_DISTRIBUTION
--preserve-metadata=identifier,entitlements,flags
"$BUILD_PATH/AppName.app/Contents/PlugIns/*.bundle"
codesign --force --verify --verbose --timestamp --options runtime
--sign $CERT_DISTRIBUTION --entitlements "$ENTITLEMENTS"
"$BUILD_PATH/AppName.app"{noformat}

  1. Resolution Note:

    The issue comes from an incorrect provisioning profile that is missing an entitlement

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.