missing 'cu' binary in v1.0.34 & v1.0.33 releases (macOS)

[craigz]

Launching the gui Goose.app on macOS generates errors loading enabled extensions.

Additionally, any attempt to enable a disabled extension results in the toggle briefly animating, then returning to the disabled state.

The following error is logged, once for each extension load attempted at application start-up:

Error invoking remote method 'get-binary-path': Error: Could not find cu binary in any of the expected locations: /Applications/Goose.app/Contents/Resources/bin/cu, /Applications/Goose.app/Contents/Resources/app.asar/resources/bin/cu

I've locally resolved the issue by copying /usr/bin/cu to the /Applications/Goose.app/Contents/Resources/bin/ directory.

Note: There was an issue with identical symptoms that was fixed a couple of releases ago, where configured extensions would not load on the initial launch of the new application version, after an update with attempts to enable them failing. However, I'm unsure of the cause nor resolution of that error, so am unsure if this missing binary issue has been visited and resolved in the past or if this is a new phenomena.

[michaelneale]

oh wow - nice one @craigz this is a tricky one and your work around explained it. Bug is that

cu: await window.electron.getBinaryPath('cu'),

as it isn't bundled (and isnt' needed in there).

[michaelneale]

should be resolved in latest