librewolf homebrew installation is damaged

[BitSynKed]

I think this occurred from the latest update to librewolf. Whenever I try to open it, the computer tells me its damaged and should be trashed.
I tried reinstalling it, and when that didn't work I also forced the cache to remove all installs so that the .dmg file would be downloaded again. Reinstalling with that newly downloaded librewolf is still damaged.
I then downloaded it manually from librewolf's website and installed to Applications, keeping both versions. The manual download works without an issue, the homebrew copy is still corrupted.
Is anyone having similar issues? Should I submit an issue to the homebrew-cask branch?

[flowoy96]

Hey, this is due to macOS's Gatekeeper. Just reinstall LibreWolf with the following flag:

brew reinstall librewolf --no-quarantine

This should solve the problem :)

[Jolg42]

Same issue here with latest version 117.0-1/librewolf-117.0-1-macos-arm64-package.dmg

I tried brew install --cask librewolf but got this damaged issue.

brew reinstall librewolf --no-quarantine was necessary to make it successful.

[Jolg42]

It looks like the tracking issue was closed

https://gitlab.com/librewolf-community/browser/macos/-/issues/19
Now moved to https://codeberg.org/librewolf/issues/issues/710

[AllThePi]

Just commenting to say this is still the case for me on 1/24/24

[justinnichols]

And still happening on Sonoma 14.4 on an M2 Macbook Air. If, perchance, any Librewolf devs see this...if we're supposed to install with --no-quarantine then perhaps the installation instructions for macOS on the main website should state this.

[gromgit]

the installation instructions for macOS on the main website should state this.

It does now: https://librewolf.net/installation/macos/#homebrew, which in turn points to https://librewolf.net/docs/faq/#why-is-librewolf-marked-as-broken

[lightnin]

Still happening Sonomo 14.5 on M3.
Would it be possible to change the brew instruction set so that we did not have to reinstall with the --no-quarantine flag after each update? Or does it require action by librewolf maintainers?

[purajit]

There isn't much that can be done, there's no way to tell Brew to install it with the same flags again, and it's not part of the formula configuration.

[mrtysn]

Same issue on M2 Max chip with MacOS Sonoma 14.6.1. The fix below still works.

brew reinstall librewolf --no-quarantine

[jchannon]

Just had to use the fix today 😢

[d33p-dev]

[SMillerDev]

It's only fixable by librewolf

[d33p-dev]

Yep sorry. I was speed running through different things and didn't even realize I stumbled onto the HomeBrew GH and not LibreWolf. Sorry, I'll remove comment.

[SniffleSneeze]

I can confirm this still work to bypass macOS security on 15.3.1 sequoia:

brew reinstall librewolf --no-quarantine 

[SMillerDev]

It doesn't actually fix anything, it bypassed macOS security to install the cask without enabling the usual security triggering.

[SniffleSneeze]

yeah apologies, I mainly wanted to bump up the tread, knowing that in the coming days LibreWolf and Brave are gonna probably be looked into.

[moonpost]

confirming latest fresh install as of today and it still immediately comes up with "librewolf is damaged..."

[purajit]

FYI another issue is that the uninstall + reinstall leaves some old metadata around permissions, making it seemingly impossible to allow screensharing. It's fixed by deleting the old permission entry and re-requesting; I now have this in my shell rc and run it after upgrades (this avoids having to reinstall or use --no-quarantine)

function fix_librewolf {
  xattr -d com.apple.quarantine /Applications/LibreWolf.app
  tccutil reset ScreenCapture org.mozilla.librewolf
}