Step fails when Apple distribution certificate is added in Bitrise (Xcode 11) about steps-ios-auto-provision

[sxua]

@iRaru you should change CODE_SIGN_IDENTITY setting in your project to Apple Developer to resolve this

[iRaru]

With version 1.4.1 I still have error with Xcode 11 machines (I tried different situations but without success -- only iPhone certificates, only new Apple certificates, both of them)

Downloading Certificates
4 certificate files downloaded, 4 distinct codesign identities included

Identify Certificates on Developer Portal
iOS Distribution certificate found: iPhone Distribution: XXX [327...]
iOS Development certificate found: iPhone Developer: XXX [287...]
Development certificate found: Apple Development: XXX [571...]
Distribution certificate found: Apple Distribution: XXX [537...]

Analyzing project
target codesign identity: Apple Development does not match to the already registered codesign identity: iPhone Developer

Error:
failed to determine project code sign identity
Stacktrace (for debugging):
/private/var/folders/6q/wgy6jtp12w5gzgm9lzcglpqw0000gn/T/bitrise201064441/step_src/lib/autoprovision/project_helper.rb:105:in project_codesign_identity' /var/folders/6q/wgy6jtp12w5gzgm9lzcglpqw0000gn/T/bitrise201064441/step_src/step.rb:44:in

'

[maxlapides]

I also had an issue with the Apple Distribution certificates. I'm not sure what was going on. I ended up manually creating an iOS Distribution certificate on developer.apple.com and manually uploading it to Bitrise.

[abarisain]

I think it's broken too but I have another error

Identify Certificates on Developer Portal
iOS Distribution certificate found: iPhone Distribution: XXXX [3261044306932433508]
Provided an older version of iPhone Distribution: XXXX certificate (serial: 3261044306932433508 expire: 2020-09-06 10:06:07 UTC),
please download the most recent version from the Apple Developer Portal (serial: 982791897806063958 expire: 2022-02-10 18:24:37 UTC) and use it on Bitrise!
Analyzing project
target codesign identity: Apple Development does not match to the already registered codesign identity: iPhone Developer
Error:
failed to determine project code sign identity
Stacktrace (for debugging):
/private/var/folders/6q/wgy6jtp12w5gzgm9lzcglpqw0000gn/T/bitrise109553777/step_src/lib/autoprovision/project_helper.rb:105:in `project_codesign_identity'

Not sure what that "does not match to the already registered codesign identity" error means.

[bitce]

Hey everyone!

These issues should be solved since #87 - so above step version 1.4.0 you shouldn't experience this problem, but please let us know what you do experience!

[nickprkins]

@sxua I've tried what you've stated and it doesn't work. I change it to the exact identity and it still gives that error

[iRaru]

@iRaru you should change CODE_SIGN_IDENTITY setting in your project to Apple Developer to resolve this

@sxua, thanks this fixed my problem ;)

[johannwerner]

I have Apple Development. Is that the same as Apple Developer?

[vassily-fr]

I have Apple Development. Is that the same as Apple Developer?

I tried both and :
iOS Developer -> bitrise auto-privisionning works
Apple Developer -> bitrise autoprovisionning Fails

Don't really understand why (or what is the differences)

[bitce]

Hi @vassily-fr, if you send us some example build, we might be able to tell, for instance you may be using an Xcode version lower than 11.0, that would explain the newer certificate not working yet.

[github-actions]

Hello there, I'm a bot. On behalf of the community I thank you for opening this issue.

To help our human contributors focus on the most relevant reports, I check up on old issues to see if they're still relevant.
This issue has had no activity for 90 days, so I marked it as stale.

The community would appreciate if you could check if the issue still persists. If it isn't, please close it.
If the issue persists, and you'd like to remove the stale label, you simply need to leave a comment. Your comment can be as simple as "still important to me".

If no comment left within 21 days, this issue will be closed.

[github-actions]

I'll close this issue as it doesn't seem to be relevant anymore.
We believe an old issue probably has a bunch of context that's no longer relevant, therefore, if the problem still persists, please open a new issue.