OpenLens
OpenLens copied to clipboard
Latest release fails to start on M1 MacBook Air
The 6.0.0 release downloads successfully but fails to start (I tried both replacing and clean reinstall, as well as re-downloading. Same result):
I'm not sure how to even start debugging this, but will be happy to help...
Which version have you tried ?
Hopefully, signed app wont have this issue
See https://github.com/electron-userland/electron-builder/issues/5850
Workaround is to run this:
sudo xattr -r -d com.apple.quarantine "/Applications/OpenLens.app"
6.0.0, as mentioned, with the -arm64.dmg binary. I just tried the Intel binary and it's working fine, albeit relatively slowly.
Confirmed both with dmg and zip. @jkroepke may want to take a look
Relevant info: https://github.com/electron-userland/electron-builder/issues/5850
This is expectable. ARM executable require a code signature.
New in macOS 11 on Macs with Apple silicon, and starting in macOS Big Sur 11 beta 6, the operating system enforces that any executable must be signed before it’s allowed to run.
This new policy doesn’t apply to translated x86 binaries running under Rosetta 2, nor does it apply to macOS 11 running on Intel-based platforms.
- https://developer.apple.com/documentation/macos-release-notes/macos-big-sur-11_0_1-universal-apps-release-notes
Looking forward for #1 here.
Interesting that it says "damaged" and not "unsafe" or "unsigned". Is there a known local workaround?
Here is the workaround https://github.com/MuhammedKalkan/OpenLens/issues/18#issuecomment-1200501408
Here is the workaround #18 (comment)
Yep, that worked for me! Maybe, if necessary, we can create crowdfunding for the developer certificate to sign binaries?
Here is the workaround #18 (comment)
Yep, that worked for me! Maybe, if necessary, we can create crowdfunding for the developer certificate to sign binaries?
That was what i ve been thinking recently. Maybe a patreon account would help. Open to alternatives if community supports it
I will also ask a cool guy if he want to give access to sign the App here.
Interesting that it says "damaged" and not "unsafe" or "unsigned". Is there a known local workaround?
Open Console.app (System Log Viewer) on Mac and start to stream Logs and open OpenLens.app, than you will see an Apple Policy Violation error.
I'd be happy to sponsor the project if sponsorship is enabled for the project.
Again, interesting this. on Mac Intel amd64 12.5, I get a clear indication of the lack of signature; wonder why a different error on arm64 only?
on amd64 12.5 👆
wonder why a different error on arm64 only?
Apple decide that the signature policy affects only native arm64 builds