Open terryjiang2020 opened 2 years ago
Same issue.
Update: This is what I set:
[20:47:49]: ------------------------------------------
[20:47:49]: --- Step: install_provisioning_profile ---
[20:47:49]: ------------------------------------------
[20:47:49]: Installing provisioning profile...
[20:47:49]: ------------------------------------------
[20:47:49]: --- Step: update_code_signing_settings ---
[20:47:49]: ------------------------------------------
+-----------------------+------------------------------------+
| Summary for code signing settings |
+-----------------------+------------------------------------+
| use_automatic_signing | false |
| path | ./platforms/ios/***.xcodeproj |
| code_sign_identity | Apple Development |
+-----------------------+------------------------------------+
This is what I received later on
[20:48:22]: ▸Clean Succeeded
[20:48:31]: ▸ ❌ error: No signing certificate "iOS Development" found: No "iOS Development" signing certificate matching team ID "***" with a private key was found. (in target '***' from project '***')
[20:48:31]: ▸ ** ARCHIVE FAILED **
And I am not using iOS Development
at anywhere.
I am having the same issue, Any solutions yet?
I am having the same issue, Any solutions yet?
No solution so far, still investigating it.
I managed to get the list of my code sign identity by just running this command:
security find-identity -p codesigning -v
and use the value there.
security find-identity -p codesigning -v
how please?
any solutions on this?
any solutions on this?
I think you are supposed to include the full common name of the signing certificate you uploaded.
In my case, that follows the format "Apple Distribution:
You can look up this name from the Mac used to create the certificate - either from Keychain Access or by running the command @alinz mentioned.
The thing is, my signing certificate is not with "iOS Development", but with "Apple Development". I have set
code-signing-identity
to "Apple Development" and replaced all possible "iOS Development" across the code, but this still happens. I wonder what issue could that be.