-
Notifications
You must be signed in to change notification settings - Fork 5.8k
codesigning fails with "unknown error -1=ffffffffffffffff" #8797
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
It seems like this issue might be related to code signing 🚫 Have you seen our new Code Signing Troubleshooting Guide? It will help you resolve the most common code signing issues 👍 |
It seems like you have not included the output of To make it easier for us help you resolve this issue, please update the issue to include the output of |
The Code Signing Troubleshooting guide did not help. Here's the
|
I believe similar issues have been solved in the past, a quick search I found #7821 (On mobile right now, it's hard to dig further into GitHub from a phone :/ ) |
Thanks, I'll check that out ASAP. |
I'll keep an eye on this post and try to help is I can. I ran into the fffffff error at one point. I remember it being an environment issue over a fastlane one, but I could be wrong. |
After setting up a new box from scratch and running into the exact same problem there, I was finally able to resolve this using the 2nd answer from this SO question. Basically, in addition to unlocking the keychain it is also necessary to run |
This may be the problem. #6866 (comment) example:
|
This certainly looks similar, but I don't think it's the same underlying problem. What really solved it for me was using |
I worked around this by creating a new keychain with a password and setting the |
My solution, Hope it will help someone. |
for those, who search for the answers (because this threads pops up in the top of google search results) in my case, the keychain contained 3 iOS Developer certificates for a single dev team, so I had to revoke them manually, delete from keychain and create a new one. These steps, resolved my issue immediately. |
Our Jenkins build server is also having this problem. Curiously,
Then... For a more detailed error log, check the full log at:
@gereons, where did you incorporate the call to |
I fixed it using advice from Apple forums. I removed Yip yip! |
@semireg In our setup, this is part of the script that Jenkins executes:
|
I had to deal with this issue years ago, and just today once again after setting up a new mac mini as a Jenkins node, and since using the Keychain app to grant all applications access to the private keys still doesn't really work under an SSH session, I've applied the same solution I had used before: run another I use the following shell script to run the additional sshd instance. I recall copying it from somewhere else and then modifying it to use password authentication instead of ssh keys to log-in.
And to run it automatically from your jenkins user account (upon logging in), add a plist file under ~/Library/LaunchAgents, e.g:
Finally update the Jenkins node configuration to use the port 2222 instead of the default 22. |
@gereons When I run |
@l-nawrocki sorry, didn't run into that, AFAIR. |
Per that Apple thread, moving the Certificate from System keychain to Login keychain fixed the -1 error for me. |
@gereons THANK YOU! Adding |
Seems like things are working well for people. I am going to close this, but please feel free to continue discussion and we will reopen if necessary!! 🚀 |
One more helpful hint: the |
New Issue Checklist
Issue Description
I'm in the process of setting up fastlane on our CI box as a replacement of the (currently broken) Xcodebuild plugin for Jenkins. Everything works fine until the last step, codesigning, which fails with "unknown error -1=ffffffffffffffff".
Last output from fastlane is
and the last lines of that file are
This only happens on our CI box (running macOS 10.12.4 and Xcode 8.3. fastlane and cocoapods are up-to-date)
Environment
Please run
fastlane env
and copy the output below. This will help us help you 👍If you used
--capture_output
option please remove this block - as it is already included there.[INSERT OUTPUT HERE]
Stack
System Locale
The text was updated successfully, but these errors were encountered: