[Bug]: Snap/Flatpak package: Browser extension not working (no native messaging)

[GleammerRay]

Bug description

Browser extension saying No connector found.
Checked the native messaging directories, manifest files are not updated as they need to be.

Expected outcome

No response

Steps to reproduce

Install snap/flatpak package, open once, use browser extension

Error log

App version

v1.5.0 - Browser Extension

Submission checklist

• I have specified the problem in the issue title
• I have provided a verbose description of the problem

[GleammerRay]

Possible fix for snap: https://forum.snapcraft.io/t/the-personal-files-interface/9357
Possible fix for flatpak:
https://docs.flatpak.org/en/latest/sandbox-permissions.html

[GleammerRay]

Working fix for Flatpak package already found, waiting for Snap problem to be solved until releasing.

[GleammerRay]

Snap package fix implemented, waiting until plug autoconnect is enabled by store maintainers: https://forum.snapcraft.io/t/autoconnect-browser-extension-connector-plug-for-passy/35705

[GleammerRay]

Snap package installation allowed with the new plug in place, no autoconnect granted. Now showing an error snackbar with a button that sends the user to https://github.com/GlitterWare/Passy/blob/dev/SNAP-STORE.md#enabling-browser-extension-support.

[GleammerRay]

Flathub package works normally (native messaging files installed in place) with the following permissions added:

- '--filesystem=~/Documents'
- '--filesystem=~/.mozilla/native-messaging-hosts'
- '--filesystem=~/.config/microsoft-edge/NativeMessagingHosts'
- '--filesystem=~/.config/google-chrome/NativeMessagingHosts'
- '--filesystem=~/.config/chromium/NativeMessagingHosts'
- '--filesystem=~/.config/BraveSoftware/Brave-Browser/NativeMessagingHosts'

Will attempt introduction of these changes with the next release.