Beaker 1.0 does not start on Big Sur / M1

[holtwick]

[paul90]

A separate build will be required for Apple Silicon support. See Electron 11.0.0, and Apple Silicon Support.

[holtwick]

Usually Electron apps seem to work fine under Rosetta (the Intel Chip emulator). For a Intel build it should still work then.

[bhaviksingh]

I have the same issue :( Commenting mostly to track

[Bluebie]

I think this might be as simple as a config problem inside some info.plist or something like that, because oddly, if you:

cd "/Applications/Beaker Browser.app/Contents/MacOS"
./Beaker\ Browser

It will open and run just fine on M1.

So whatever the issue is must be some kind of validation happening when we try to launch the app graphically from it's icon in Finder/mac UI stuff. The process works fine.

I have no idea how to debug this, though. macOS is not very helpful when it comes to error messages.

[Bluebie]

Attempting to launch Beaker 1.1 on macOS 11.2.1 on M1 MacBook Air via Finder icon results in the system console logging four messages that seem related to the launch task:

default	09:04:56.924024+1100	Finder	Found application <private> to open application <private>
error	09:04:56.927611+1100	Finder	LAUNCH:Application cannot be launched because its unsupported bit is set, com.bluelinklabs.beaker-browser node=<private> status=-10661
error	09:04:56.928092+1100	CoreServicesUIAgent	handle LS launch error: {\n    Action = oapp;\n    AppMimimumSystemVersion = "10.10";\n    AppPath = "/Applications/Beaker Browser.app";\n    ErrorCode = "-10661";\n}
default	09:04:56.929802+1100	CoreServicesUIAgent	Connection from process 7855 does not have the required entitlement com.apple.private.iscsuia

[soapdog]

Just to flag that this is still happening. With M1-based macs becoming more common and eventually the norm, this might be something worth looking into.

[whoisgina]

Hi there! Wow, Beaker is so new and fresh and shiny now! ✨

I'm also not able to launch Beaker from Finder on an M1 Mini running macOS 11.1, with very similar system console errors:

default	12:23:11.646919-0700	Finder	Found application <private> to open application <private>
error	12:23:11.648736-0700	CoreServicesUIAgent	handle LS launch error: {\n    Action = oapp;\n    AppMimimumSystemVersion = "10.10";\n    AppPath = "/Applications/Beaker Browser.app";\n    ErrorCode = "-10661";\n}
error	12:23:11.648302-0700	Finder	LAUNCH:Application cannot be launched because its unsupported bit is set, com.bluelinklabs.beaker-browser node=<private> status=-10661
default	12:23:11.651051-0700	CoreServicesUIAgent	Connection from process 529 does not have the required entitlement com.apple.private.iscsuia

I'm bumping this specifically because I'm running a remote Beaker workshop for a group of designers and developers, and a few of them have M1-based machines. I can launch it from the command line just fine, but would love for my audience to not have to do that, as it'll be a mixed room in terms of command line comfort, and ease of use is why I'm trying to sell them on Beaker in the first place, ha!

I don't have any macOS dev experience, but if there's any other way I could help y'all figure this out, I'd be happy to do so!

[aeschylus]

electron-userland/electron-builder#5397

[entangledothers]

Same issue on Monterey / M1, sadly unable to open due to not being supported.

[srikumarks]

On Monterey (MacOS 12.0.1), I can alias the executable and launch it just fine from shell - like so --

alias beaker=/Applications/Beaker\\\ Browser.app/Contents/MacOS/Beaker\\\ Browser

but I do get the error on a standard double-click launch. A bit of head scratcher with a likely easy fix. Was wondering whether its requirement to access local network might be a problem with the recent OS.

[khirsch]

Guessing this hasn't been solved yet? I'm having the same issue, running Monterey 12.6.1 with the M1 chip.