Not Working on MACOS #526

It says the disk image is damaged and that I should eject it for me, too.

I have the same issue, on Imac M4 24" 16GB, iOS Tahoe 26.1
Doesn't work !!!

you CAN do xattr -dr com.apple.quarantine /Applications/libresprite.app in macos terminal after you drag the app into your applications to unquarantine it, but the app instantly kills itself

Hey guys, I'm a copy paste noob. I got it to work with the help of Claude. I used these three commands and got it working perfectly on my computer. Again, this is AI, so use at your own risk. Worked for me!

Fix for "libresprite.app is damaged and can't be opened" on Apple Silicon (M1/M2/M3/M4). Tested on macOS Tahoe 26.3.1, MacBook Air M3.

The downloaded build isn't notarized, and on Apple Silicon every executable and dynamic library must carry at least a valid ad-hoc signature — otherwise the loader refuses it and the process is killed silently. These three commands clear the quarantine flag and ad-hoc sign the bundle and its libraries locally. No Apple servers are contacted and nothing outside the LibreSprite bundle is touched.

Run each command in Terminal. If your /Applications folder isn't user-writable, prefix each with sudo.

Step 1: Remove the Gatekeeper quarantine attribute

xattr -dr com.apple.quarantine /Applications/libresprite.app

Explanation: This strips the macOS quarantine flag that Gatekeeper applies to files downloaded from the web, resolving the initial "app is damaged and can't be opened" error. (If you prefer, xattr -cr /Applications/libresprite.app also works — it clears all extended attributes instead of only the quarantine one.)

Step 2: Ad-hoc sign the bundled dynamic libraries

find /Applications/libresprite.app/Contents/libs/ -name "*.dylib" -exec codesign --force --sign - {} \;

Explanation: LibreSprite ships its dependencies in a non-standard Contents/libs/ folder instead of Contents/Frameworks/. codesign --deep doesn't reliably re-sign loose .dylib files in non-standard locations (and Apple now recommends against --deep for exactly this kind of reason), so we sign each library directly. On Apple Silicon, any .dylib with a missing or broken signature causes the kernel to terminate the process at load time — that's the zsh: killed you see if you skip this step. The lone - after --sign means "ad-hoc" (local signature, no certificate, no identity).

Step 3: Ad-hoc sign the main application bundle

codesign --force --sign - /Applications/libresprite.app

Explanation: With the internal libraries now validly signed, this applies a fresh ad-hoc signature to the top-level app bundle so macOS will let it launch.

After these three commands, LibreSprite should launch normally from Finder or Launchpad. ⚠️ Only run this on a build downloaded from the official LibreSprite releases page — ad-hoc signing will happily sign anything, including malicious binaries, so only use it on code you trust.