Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add support for defining code sign entitlements per configuration #5940

Closed
anlaital-oura opened this issue Feb 16, 2024 · 0 comments · Fixed by #6293
Closed

Add support for defining code sign entitlements per configuration #5940

anlaital-oura opened this issue Feb 16, 2024 · 0 comments · Fixed by #6293
Labels
good first issue Good for newcomers type:need/problem Report needs or problems you came across that are not bugs

Comments

@anlaital-oura
Copy link
Collaborator

What problem or need do you have?

Currently it is not possible to have code sign entitlements that differ between configurations. The use case for having separate ones is, for example, that you have multiple backend configuration and you want to have separate values for keys such as com.apple.developer.associated-domains.

Xcode already supports defining CODE_SIGN_ENTITLEMENTS for each configuration separately.

Related thread on Slack.

Potential solution

No response

macOS version

14.3.1

Tuist version

4.2.3

Xcode version

15.2
@anlaital-oura anlaital-oura added the type:need/problem Report needs or problems you came across that are not bugs label Feb 16, 2024
@pepicrft pepicrft added the good first issue Good for newcomers label Feb 21, 2024
lucasmpaim added a commit to lucasmpaim/tuist that referenced this issue May 16, 2024
@lucasmpaim
Add capability to set CODE_SIGN_ENTITLEMENTS on XCConfig
977a0fd 
fix for tuist#5940

Currently xcode don't have a good support for variables inside of a entitlement value, causing a issue in projects with multiple environments and appclip
lucasmpaim added a commit to lucasmpaim/tuist that referenced this issue May 16, 2024
@lucasmpaim
Add capability to set CODE_SIGN_ENTITLEMENTS on XCConfig
98857f9 
fix for tuist#5940

Currently, Xcode don't have a good support for variables inside an entitlement value, causing an issue in projects with multiple environments and appclip
lucasmpaim added a commit to lucasmpaim/tuist that referenced this issue May 16, 2024
@lucasmpaim
Add capability to set CODE_SIGN_ENTITLEMENTS on XCConfig
ade0350 
fix for tuist#5940

Currently, Xcode don't have a good support for variables inside an entitlement value, causing an issue in projects with multiple environments and appclip
@lucasmpaim lucasmpaim mentioned this issue May 16, 2024
Merged
6 tasks
pepicrft pushed a commit that referenced this issue May 21, 2024
@lucasmpaim
Add capability to specify variable entitlements (#6293)
a647f6f 
* Add capability to set CODE_SIGN_ENTITLEMENTS on XCConfig

fix for #5940

Currently, Xcode don't have a good support for variables inside an entitlement value, causing an issue in projects with multiple environments and appclip

* rename entitlement.xcconfig to entitlment.variable

also add a new unit test to test variable set by string literal

* expand docs for Entitlement.variable
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
good first issue Good for newcomers type:need/problem Report needs or problems you came across that are not bugs
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Add capability to specify variable entitlements lucasmpaim/tuist
2 participants
@pepicrft @anlaital-oura