ERROR ITMS-90334: "Invalid Code Signature Identifier."

[frogg]

While uploading an app to iTunes Connect I receive the following error message within Xcode:

ERROR ITMS-90334: Invalid Code Signature Identifier. The identifier "com.sindresorhus.LaunchAtLoginHelper" in your code signature for "LaunchAtLoginHelper" must match its Bundle Identifier "io.frogg.my.app"

Any idea what's going on here?

[sindresorhus]

This should have been fixed in v3.0.1. What version are you using?

[frogg]

Thanks, that's good to know! I've been using the Swift Package Manager branch which does not include the mentioned fix so far I assume. I have now merged the latest version of your repo into that branch locally and will give it another try!

[sindresorhus]

Did you manage to resolve the issue?

[frogg]

Did you manage to resolve the issue?

Unfortunately, not. Even with the latest commits merged into the Swift Packet Manager Branch, the problem still exists for me.

[sindresorhus]

Then it might be a separate problem with that PR.

// @SergeyKuryanov

[sindresorhus]

I'm successfully using v4 in a shipping App Store app and I did not encounter this problem.

[frogg]

Unfortunately, I still get this error when I attempt to upload to iTunes Connect:

[frogg]

Ok, I figured it out. After getting the code signing issue I checked the output of the script. And apparently the signing of LaunchAtLoginHelper failed, because I had two similar certificates for this TeamID stored in my keychain and it failed to pick one. I deleted the older one, and now it seems to work! Sorry for the confusion. I hope this might help someone in the future.

[zddhub]

I met this issue as well, I used v4.2.0 and Xcode Version 13.4.1 (13F100), Any thoughts?

[zddhub]

Ignore me, I had another certificate in my keychain as well. After deleting it, it works for me as well.

[codeandclay]

@zddhub I have the same problem. I've deleted some certificates in my keychain but I'm not sure if they're the right ones. What certificates should I look for?

[zddhub]

@codeandclay , Maybe just keep on certificate in keychain list and have a try

[342261733]

same problem