Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
XM forcing provisioning with custom entitlements when Xcode does not #5061
Steps to Reproduce
XM signing to match Xcode signing.
Signing requires differ.
It's worth noting that, if you have a (Mac) provisioning profile, then it's possible to use None in the UI.
IOW the current code makes a difference between None (where no
referenced this issue
Jan 16, 2019
@albilaga there's an UI issue in VS Mac where you cannot select None without having a provisioning profile.
However you do not need to use it when signing your application, i.e. create a profile and then select None and it should be identical to what Xcode does. If not please provide us with a test case so we can investigate this further. Thanks!
@spouliot you actually can’t do that. If you do that you actually still embed provisioning profile in mac.app. It is different with what XCode does when you use none in XCode it will not embed provisioning profile. You can try to Show Package Content in app that build with signing application bundle but with provisioning profile set to None. There is still embedded.provisionprofile inside the app which is different from xcode build app which there is no embedded.provisionprofile inside it
- <_RequireProvisioningProfile Condition="'$(CodesignEntitlements)' != ''">True</_RequireProvisioningProfile> + <_RequireProvisioningProfile Condition="'$(CodeSignProvision)' != ''">True</_RequireProvisioningProfile>