-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
self-signed codesigning certificate? (mac) #458
Comments
In our tests we use self-signed cert too. But it is supported only if you specify
|
Please try to make your self-signed cert as trusted using keychain (it must be green). Otherwise it is not valid and, so, not returned. |
Hey Vladimir, doesn't work for me either. Same problem. I've created code signing certificate from Keychain Access. In release notes, I've seen:
Can this be an issue? |
@Vj3k0 Yes, should be fixed. |
@develar that solved it, thanks ! ❤️ |
@develar - THANK YOU! |
Anyone know how to use Mac Developer: XXX (YYYY) to sign? If I create my own certificate and make it trusted so it appear on (security find-identity -v -p codesigning), I can sign my Apps without any problem. The problem only exist when using Mac Developer: XXX (YYYY) to sign the app Update: |
@LckySndays It is forbidden currently, please vote for #812 |
I created a certificate via keychain access > certificate assistant > create a certificate. (in the login keychain)
Then I type the following in the terminal before building;
export CSC_NAME="My Test Certificate"
But output is:
Identity name "My Test Certificate" is specified, but no valid identity with this name in the keychain
What is the problem? Is it not possible to use a self-signed certificate?
The text was updated successfully, but these errors were encountered: