"Code Signing Entitlements" (CODE_SIGN_ENTITLEMENTS) should be set on the target level instead of project level. This results in the signing entitlements to point to the same file when creating a new target.
Problem
This creates a problems where if you add a Capability in Xcode to either your new target or the main Cordova one it is added to all other ones.
What is expected to happen?
I would expect a .entitlement for each target.
What does actually happen?
"Code Signing Entitlements" get set on the "Project" instead of each target to $(PROJECT_DIR)/$(PROJECT_NAME)/Entitlements-$(CONFIGURATION).plist.
Information
If you create a new Xcode project you can see the "Code Signing Entitlements" is set at the Target level instead of Project.
Project Level is blank:
Bug Report
"Code Signing Entitlements" (CODE_SIGN_ENTITLEMENTS) should be set on the target level instead of project level. This results in the signing entitlements to point to the same file when creating a new target.
Problem
This creates a problems where if you add a Capability in Xcode to either your new target or the main Cordova one it is added to all other ones.
What is expected to happen?
I would expect a
.entitlement
for each target.What does actually happen?
"Code Signing Entitlements" get set on the "Project" instead of each target to
$(PROJECT_DIR)/$(PROJECT_NAME)/Entitlements-$(CONFIGURATION).plist
.Information
If you create a new Xcode project you can see the "Code Signing Entitlements" is set at the Target level instead of Project. Project Level is blank:
Target level is set for main target:
My other target has it's own file:
Cordova code reference
The value is being assigned here: https://github.com/apache/cordova-ios/blob/6.2.0/bin/templates/scripts/cordova/build.xcconfig#L43 However the change isn't simply updating this value (as I don't believe Xcode has a
$(TARGET_NAME)
place holder.Version information
Checklist