-
Notifications
You must be signed in to change notification settings - Fork 45
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
"Caspion cannot be opened..." #MacOS #Big_Sur #M1 #276
Comments
@tbendr I have a new release to test on M1 before I will publish it. Do you want to try? If so, please contact me inMail, it is a big file. baruchiro@gmail.com |
@tbendr I understand the artifact is working? |
is this issue being worked on? i tried to to install dependencies via yarn and got an error:
after trying to implement the changes in PR #277 i got this error:
|
@hannanel100 @tbendr Please check https://github.com/brafdlog/caspion/releases/tag/v0.2.0 if it works on your M1. |
It does, Thanks!! To open it you need to:
|
Thanks @tbendr! I will add it to the README file. |
Closed by #378 |
I saw it too! Now I know there is a problem. Meanwhile, I installed the previous version. |
What was only a warning for unsigned apps on the Intel chip became to be a damaged app on the Apple chip. To sign it with an empty signature and get the warning back:
Then, right-click on the app and select I will keep this open until we will solve it. Need to add the explanation above to the documentation. |
Issue has been marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
I prefer to keep this open, we are still using the comments here. |
by @ariel-wiz on #620 |
Caspion for mac
I downloaded "caspion-0.0.6-beta-mac.zip".
I get this error whenever I try to run the app on my M1 Mac Mini (macOS Big Sur).
Does Caspion support M1 chips?
The text was updated successfully, but these errors were encountered: