Skip to content
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

macOS ARM binaries are corrupted and won't open #560

Open
muskit opened this issue Apr 1, 2024 · 5 comments
Open

macOS ARM binaries are corrupted and won't open #560

muskit opened this issue Apr 1, 2024 · 5 comments
Labels
bug Something isn't working

Comments

@muskit
Copy link

muskit commented Apr 1, 2024

The latest ARM release for macOS (3.2.6; January 28, 2024) won't open due to it being "damaged" according to the OS.

To Reproduce

  1. Download any of the ARM packages for macOS (3.2.6).
  2. Extract the .app.
  3. Attempt to run the app.

Expected behavior
The app opens.

Result
Screenshot 2024-03-31 at 11 32 54 PM

Tested on a MacBook Air (M1, 2020) running macOS Ventura 13.4. Tried both the .zip and .dmg arm64 releases.

The x86_64 binary running via Rosetta 2 works perfectly fine, though the titlebar was hidden until I went to ArmCord settings and set the theme to "Native."

@muskit muskit added the bug Something isn't working label Apr 1, 2024
@BluePurplePro
Copy link

BluePurplePro commented Apr 10, 2024

sudo spctl --master-disable

If it won't open, try this instead:
xattr -cr /path/to/application.app

@muskit
Copy link
Author

muskit commented Apr 16, 2024

sudo spctl --master-disable

If it won't open, try this instead: xattr -cr /path/to/application.app

This worked! Looks like it could be solved by signing at build time, but that probably costs money...

@BluePurplePro
Copy link

"If macOS detects that software has been modified or damaged, your Mac notifies you that the app can't be opened" said by Apple Support :kekw:

@Vendicated
Copy link
Contributor

just fyi, the app is not corrupted, modified or damaged in any way. this is just apple deciding that they don't like the app and randomly flagging it, then making it seem like it's the developer's fault

the only way to solve it is to sign, which costs 100$ a year
xattr -cr /path/to/application.app should work though

@muskit
Copy link
Author

muskit commented Apr 25, 2024

So looks like Apple just made it way more security-paranoid with unsigned apps on ARM to the point of refusing to open...

thaaaanks....

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants