-
Notifications
You must be signed in to change notification settings - Fork 18
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
Cannot start ARM M1 binary package (but build it ok) #51
Comments
Probably not related but I tried to install it by cloning the GitHub and build from source. Cloning via Github Desktop produce this error:
I am not that interest but if the binary is not working in Arm M1, may have to go this path one day or today:
It works and as a surprise I cannot see the directory in finder except jump to it via finder folder command, until later ...! How can it be? Anyway the built one is the standalone version it works, except one has to use git command line not desktop and has to build it oneself. And have to find out how to get the other part. And I hope the version in the app is ok and hence just copy those 2 into my standalone app and run it from there !! |
I cannot reproduce the error on macOS ARM, can you launch Gupax from the command-line and post the output? Also for git, you may need to use git clone --recursive https://github.com/hinto-janai/gupax |
I have the same issue with M1 Max, I might take the time to build it but this isn't ideal as Gupax aimed to be an easy solution ^^ |
This issue is related to Apple's security features. Apps downloaded from the Internet may be flagged as 'unsafe' if they lack proper notarization by Apple, a process that requires an active Apple Developer Program membership. Source: As a workaround you can remove the quarantine flag on the .app file by running the following command in your terminal:
(Replace |
Thanks for the info. IIRC, the Apple Developer Program requires real world identification and a fee? |
The membership is $99/year, and I'm not sure about the real world identification, but guess it does require it. |
Describe the bug
cannot start the ARM M1 (Intel is ok)
To Reproduce
Steps to reproduce the behavior:
Screenshots
OS & Version:
macOS 13.5.2
I finally built one myself and hence I resolve the issue. I am not sure others want to do this as well.
The text was updated successfully, but these errors were encountered: