sindresorhus / LaunchAtLogin-Legacy

Add “Launch at Login” functionality to your macOS app in seconds
MIT License
1.54k stars 119 forks source link

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

Open frogg opened 3 years ago

frogg commented 3 years ago

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"

Screenshot 2020-08-28 at 23 55 40

Any idea what's going on here?

sindresorhus commented 3 years ago

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

frogg commented 3 years ago

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 commented 3 years ago

Did you manage to resolve the issue?

frogg commented 3 years ago

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 commented 3 years ago

Then it might be a separate problem with that PR.

// @SergeyKuryanov

sindresorhus commented 3 years ago

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

frogg commented 3 years ago

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

frogg commented 3 years ago

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 commented 1 year ago

Screen Shot 2022-08-09 at 20 47 11

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

zddhub commented 1 year ago

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

codeandclay commented 1 year ago

@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 commented 1 year ago

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

342261733 commented 4 months ago

same problem