Actually, you probably don’t really need that dbus slot. We recently submitted a fix to flutter which prevents that from being a fatal error. See Flutter Snapcraft.yaml - #10 by kenvandine for details.
You can apply this manually in your project with the following patch:
diff --git a/linux/my_application.cc b/linux/my_application.cc index 3ad3281..8b02ceb 100644 --- a/linux/my_application.cc +++ b/linux/my_application.cc @@ -42,5 +42,6 @@ static void my_application_init(MyApplication* self) {} MyApplication* my_application_new() { return MY_APPLICATION(g_object_new(my_application_get_type(), "application-id", APPLICATION_ID, + "flags", G_APPLICATION_NON_UNIQUE, nullptr)); }
This will allow your application to start without trying to own the name on dbus. You can then drop the dbus-svc slot you have defined, which will ease getting it in the store.