Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Command /usr/bin/codesign failed with exit code 1

I have the following error:

Command /usr/bin/codesign failed with exit code 1

Here is what I already did for trying to fix this:

  • set the bundle identifier to com.server.pgmname
  • set the code signing to "Any Iphone OS Device"
  • set the Code Signing Identity to my Distribution identity.

The error only occurs when I try to build on my device, on the simulator everything works fine.

Do you have any suggestions?

like image 422
Daniel Avatar asked Jan 07 '10 02:01

Daniel


3 Answers

I had the exact same error, and tried everything under the sun, including what was suggested elsewhere on this page. What the problem was for me was that in Keychain Access, the actual Apple WWDR certificate was marked as "Always Trust". It needed to be "System Defaults". That goes for your Development and Distribution certificates, too. If any of them are incorrectly set to "Always Trust", that can apparently cause this problem.

So, in Keychain Access, click on the Apple Worldwide Developer Relations Certificate Authority certificate, select Get Info. Then, expand the Trust settings, and for the combo box for "When using this certificate:", choose "System Defaults".


Sigh: for those insistent on downvoting this answer, I am not claiming this to be the only solution for this problem. It's one solution. It may not work for you. There are multiple reasons for this codesign failure.

like image 165
Nate Avatar answered Nov 04 '22 09:11

Nate


I had the exact same problem and this did the trick for me:

Xcode > Preferences > Accounts > View Details > And just refresh the Provisioning Profile

Seems like the accounts in Xcode were not updated with the latest provisioning profiles so a quick refresh sorted this out.

like image 38
mgm Avatar answered Nov 04 '22 08:11

mgm


Feel the need to share this, even though it's ridiculous.

I'd set up a second developer account on my Mac and couldn't codesign anything. The error was "the user cancelled the operation".

A simple reboot fixed this for me.

like image 29
Chris Newman Avatar answered Nov 04 '22 08:11

Chris Newman