Auto-connection request for network-manager for mccompanion
name: mccompanion
description: MCCompanion is a feature-rich Minecraft companion application.
Ping and monitor your servers, browse the wiki, manage skins, and more.
snapcraft: https://github.com/MCCORG/MCCompanion/blob/linux-prework/snap/snapcraft.yaml
upstream: https://github.com/MCCORG/MCCompanion/tree/linux-prework
upstream-relation: member & collaborator
plugs:
network-manager:
interface: [optional] one of https://snapcraft.io/docs/reference/interfaces/
attributes: [optional] interface attributes if any
request-type: auto-connection
reasoning: The application relies on the official Flutter `connectivity_plus` plugin to verify real-time network connectivity before initiating background Minecraft server pings and local proxy routines.
On Linux desktop environments, `connectivity_plus` interfaces directly with NetworkManager via system D-Bus (`org.freedesktop.NetworkManager`) using `org.freedesktop.DBus.ObjectManager.GetManagedObjects`.
When strictly confined without an active `network-manager` connection, AppArmor intercepts these method calls with `AccessDenied`, preventing the app's startup connectivity checks from running properly and throwing unhandled D-Bus exceptions out-of-the-box.
We use this interface strictly for read-only connectivity monitoring to handle online/offline transitions gracefully.
If the access needed is read-only connectivity monitoring, have you tried the network-manager-observe interface? The observe interface is preferred as it is a narrower scope, and would be an easy approval for auto-connection. If you have tried it and run into issues, please describe them here. Thank you!