-
Notifications
You must be signed in to change notification settings - Fork 240
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
Can't run crc setup on macOS Catalina - "the developer cannot be verified" #836
Comments
Probably related: hashicorp/terraform#23033 Workaround is to:
CRC (the binary—any command) seems to run very slowly under Catalina, though. Could be related to #727 So, since there's a workaround, the question is: is it possible for CRC to be signed by a valid developer account (I believe you can get a Developer ID free with any working Apple ID, and use it to sign apps to bypass Gatekeeper) during its build process, so macOS users don't have to go through these hoops to use it? |
@geerlingguy Yes we are working on that, we will prioritise it in next sprint. |
I can confirm that I can reproduce this issue after upgrading to Catalina. |
FYI: Could reproduce with CRC V1.4.0 |
FYI: Could reproduce with CRC V1.6.0 |
Binaries haven't been signed yet. Use the provided exception option as
referenced by Apple on the dialog.
…On Wed, Feb 19, 2020 at 8:55 PM Sebastian Faulhaber < ***@***.***> wrote:
FYI: Could reproduce with CRC V1.6.0
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
<#836>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAAOZWBOU7NWKTMCNBBP6DRDUT3BANCNFSM4JQSLW5A>
.
--
Gerard Braad | http://gbraad.nl
[ Doing Open Source Matters ]
|
Here's how VSCode did it...maybe this helps: https://developer.apple.com/documentation/xcode/notarizing_macos_software_before_distribution I still think that the workaround is not acceptable for many customers. So I kindly ask you to put this up in the list. Thanks a lot. Regards, |
this is being resolved company wide, but some applications are currently in the process for this. we will hopefully soon |
My corporate IT admin sadly setup my mac and disabled the prompt for me to trust the crc app, so I had to allow download for all apps with "sudo spctl --master-disable". |
My workaround is to simply remove the quarantine flag, after which crc runs without issues:
I usually create a symlink so that I don't have to keeping typing in "dot" "slash" (i.e.
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
FYI - could reproduce with 1.19 on Mac |
We are now shipping a .pkg for macOS. The crc binary is now signed and notarized. The default link will be changed in couple of days. https://mirror.openshift.com/pub/openshift-v4/clients/crc/latest/crc-macos-amd64.pkg |
Default link is now the pkg |
General information
crc setup
before starting it? Yes (but that's where it fails)CRC version
CRC status
CRC config
Host Operating System
Steps to reproduce
$PATH
(mv ~/Downloads/crc-macos-1.1.0-amd64/crc /usr/local/bin/crc
)crc setup
Expected
I would be guided through the CRC setup process.
Actual
After about a minute, I see the following dialog pop up:
It reads:
Logs
N/A - crc won't run
The text was updated successfully, but these errors were encountered: