Redundant client objects created
After MR !13 (merged), if the application process stays alive, it's client object is kept around so if they call
GetClient() again, they'll get a new client but the old one is still around. While this is a desired behaviour for the Flatpak portal, it's not for system apps (e.g gnome-settings-daemon).
One way to solve this w/o breaking API, would be to add a new property (e.g
Client that dicates whether or not to re-use it. For API compatibility, it'll be
true by default and Flatpak portal will have to set it to false.