Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Installing from homebrew on Apple Silicon mac shows "damaged" error
See original GitHub issueDescribe the bug
Running kui from a brew install kui on an M1 (Apple Silicon) Mac results in the following error upon first open. Unknown if the arch is related.
Steps to reproduce the behavior
brew install kui- Open Kui.app
Expected behavior Normal app open
Screenshots
System
Kui: 10.8.2 (latest)
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (4 by maintainers)
Top Results From Across the Web
Homebrew - Chromium is damaged and can't be openend
I'm trying to install LibreWolf and Chromium on a M1 Air through Homebrew. Both browser show the same error when trying to start...
Read more >Not able to install homebrew on my m1 macbook
install HomeBrew from terminal Homebrew: /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)" ...
Read more >Xcode fails to start Loading a plug-in failed. - Apple Developer
Problem : Xcode fails to launch with following alert: "Loading a plug-in failed. -- The plug-in or one of its prerequisite plug-ins may...
Read more >Why does my brew installation not work? - Ask Different
I had the same problem—installed brew, used it, but now it doens't work, ie, brew command not recognized anymore.
Read more >How to Fix App “is damaged and can't be opened. You should ...
The first thing you should do to try and remedy the “app damaged” error message is to re-download the app to the Mac,...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Heya, Kui 11.0.0 was just released (
brew upgrade kui), and those builds are now signed and notarized on macOS. In our testing, this seems to have resolved the bug described in this issue! 🤞Interesting, thanks for this info. Until we can figure out how to work around the underlying Electron-macOS bugs (this delay in electron fixing this seems to stem from an underlying macOS bug), using signed builds results in some substantial slowdowns. Ugh. We’ll look into this as soon as we can.