/usr/bin/codesign failed with exit code 1

Update:
The Technical Note in my original answer is now deprecated. Apple posted a collection of code signing problems (and some solutions) in a new document: Technical Note TN2407 Code Signing Troubleshooting Index

Check the CODE_SIGN_IDENTITY property in your build settings. Is your provisioning profile selected there?
You also need to enter a valid bundle identifier in your apps .plist.
The identifier has to match the one you provided when generating the profile.
Apple has a technote about that here.

I just came across this error, and here's what I found out in case this helps anyone: I discovered that you can right click the error message in Xcode and choose expand to get more details, including a description of the problem.

In my case, I had two copies of my developer certificate with the same name in different keychain files, and Xcode couldn't figure out which one to use.

It might be strange answer for codesign issue in Xcode 9.0. I was receiving this error too and did not know what to be done, because everything was correct.

I went to the keychain, I had the login option "unlocked". I locked it and compiled my build again. Xcode itself asked me to open access keychain. I gave access and it worked.

Steps were:

1. Go to keychain
2. Lock it
3. Archive the code, build the project again

There could be a lot of reason when you get this kind of error:

1. Check whether you have selected a provisioning profile which includes the valid Code Signing Identity and a valid Bundle Identifier in Settings. (Goto Build Settings->Signing->Provisioning Profile).

2. Open Keychain Access and click on lock icon at top left, so it will lock the login keychain and then again click to unlock.

3. Goto File->Project Settings->Derived Data and delete your project build folder. After that clean and build your app.

I had the same unknown error from codesigning that you mentioned. Similar to the answer provided (but a little different), I just locked my keychain access and unlocked it, and I was able to build and run to my device again. If anyone has the same issue, perhaps try that first before going through the trouble of modifying the keychain password.

Throwing my comments into the ring, I just came across this after attempting to refresh my development environment after clicking DENY accidentally on one of the application requests, after searching around I found a number of things that didn't seem to work. This is the full order in which I've attempted the fixes and whether there was a success:

1) Attempted to clear the DerivedFiles and restart XCode - no dice

2) Attempted to Log and Unlock the Keychain, then restart XCode - no dice

3) Attempted to refresh my developer account within XCode - no dice

4) Bit the bullet and just reset my entire keychain, after doing so my developer account was signed out (signed back in), then restarted XCode - no dice

5) Found an article on here that said that we needed to set the [login|local|System]/certificate/Apple Worldwide Developer Relations Certificate Authority to "System default". But in my case it was already set to system default - no dice

6) Then I looked at my actual developer certificate login/my certificates/Mac Developer: and when I looked in there it was correctly set to Confirm before allowing access BUT there was no entries in the lower section. There should be [Xcode, codesign, productbuild]. I deleted the certificate entry and restarted XCode - bingo

The certificate was added and I was then prompted. So what did I do, I pressed "always allow" and then just boned myself.

I had to go back and delete the certificate again, then go through about 20 allow dialogs during a clean build. Once completed, I was able to build completely.

In My Case, after a fews days of research,

All I did to revolve is listed below:

1. delete all the certificate on your keychain.
2. goto your apple account. a) download the specify certificate your want to install on your keychain. b)(Optional) Also create and download the require profile.
3. in Xcode, clean your project. This may take some time.
4. Build your project.

This should work for similar codesign issues.

Note, during this process the OS would ask for your credential validation.

I use Xamarin and for me this is what worked after trying everything else. In Visual Studio for Mac I've opened a .xib file so it opens the project in Xcode.

Went to the project settings > Signing and Capabilities, selected the team and then fixed the Signing Certificate.

I think the issue is with the Keychain Access and certificate trust.

Try adding the following certificate Apple Worldwide Developer Relations Certification Authority from https://www.apple.com/certificateauthority/ (Expiry validity 2030)

The trust warning indicated in certificate will be fixed and then try building the iOS application again