I have been going back and forth in Cannot publish an electron app for many days trying to figure out how to get my Electron app to work with Snap. I eventually moved from electron-forge to electron-builder, just for the Snap build, and did some workarounds to be able to build
--destructive-mode and I now have a built Snap app published with the name
However, as part of the Electron app, we bundle the
scrot binary as part of
electron-color-picker. When we try to execute it, it does not seem to have the permissions it needs to run under Snap.
Is there a way to whitelist binaries shipped with the app or do we need to somehow use a stage package instead or something?
This is where the
scrot binary is called in electron-color-picker https://github.com/mockingbot/electron-color-picker/blob/master/source/linux/linux-scrot/index.js#L7. My first thought was perhaps we could make that path configurable, and ship
scrot as a stage package in the Snap app, then switch the path out.
My next thought was we could add the existing bundled
scrot from inside electron-color-picker to the `parts for the app or something. Perhaps something like:
parts: scrot: plugin: dump source: app/resources/app.asar.unpacked/node_modules/electron-color-picker/library/linux/linux-scrot/scrot
This is all purely speculation, as I am not very familiar with Snap, and I would love some help figuring out how to successfully get this binary to run please! Thanks in advance!