The intention of this post is to highlight some outstanding issues, and hopefully get them priortised, that would help improve snap support for developers building on Electron.
There are a couple of other issues I’m tracking that I need to re-test as a result of some recent updates, but here’s what I have so far.
Missing gnome-keyring / kwallet (secret service) interface
Several very popular applications require the use of
gnome-keyring for securely storing user credentials. There is no interface for this right now, the effect is some applications require entry of authentication credentials everytime the application is started while others simply don’t function correctly at all.
Strictly confined snapped desktop applications can’t toggle Launch at Login
I’ve a PR in progress for the desktop-helpers that works similarly to desktop-exports#L158 that symlinks
~/.config/autostart but I suspect an existing interface needs extending or an additional interface creating?
snapd-xdg-open in Trusty and other distros
This issue is well understood and a lengthy discussion is active in this forum. To breifly recap, many Electron applications need to facility to open URIs and currently this capability only exists in Ubuntu 16.04 and newer.
Media Keys do not work in strictly confined snaps
There are several (one in particular) desirable media streaming applications built on top of Electron or Chromium framework that can integrate with media keys. However, the media keys are not being exposed so it is not possible to skip tracks or play/pause using media keys.
snapcraft fails if desktop file included “ascii” cannot decode byte
Many Electron applications have translated strings in their
.desktop files for the Name, GenericName or CommentName fields. Some of the translatated strings include UTF-8 characters and this causes
snapcraft to fail.