Hi Snapcraft reviewers,
I’m requesting a manual review for my snap sparrow-app, which uses strict confinement and declares the dbus interface to support single-instance functionality via Tauri’s single-instance plugin. This plugin ensures only one instance of the application runs at a time and relies on a custom D-Bus name. This was required as we use deeplink for login purpose, without this interface the app opens new instance everytime we try to login.
Repository Link: GitHub - sparrowapp-dev/sparrow-app: Your next-gen API testing and development tool.
Snap link: https://sparrow-assest.s3.us-east-1.amazonaws.com/snap/sparrow-app_2.25.0_amd64.snap
Snap Details
- Name: sparrow-app
- Version: 2.25.0
- Base: core24
- Confinement: strict
Relevant Interfaces
Slots
single-instance:
interface: dbus
bus: session
name: org.dev_sparrowapp_desktop.SingleInstance
Plugs
single-instance-plug:
interface: dbus
bus: session
name: org.dev_sparrowapp_desktop.SingleInstance
Additional Information
This D-Bus name is used exclusively by the app for managing internal instance state and does not expose or interact with any system or third-party services. The service name follows Tauri’s naming convention and is unique to this application.
I believe this use case falls under the category of safe, self-contained dbus usage and would appreciate a manual review to enable publication with strict confinement.
Please let me know if you need any further clarifications or updates to the snapcraft.yaml.
Thank you!