Open wjt opened 4 years ago
Thanks Will for filing. I was running into that too. Your suggestion using Flatpak UpdateMonitor API to monitor when updates are available sounds great.
@dylanmccall am I right in thinking that there was a change in this area somewhere?
There has not been, no. There's some added friction around this because update notifications are used for other useful things, as well. So for the application these are generic pingbacks from the telemetry server. And we don't want to disable those. This could work better as a change in Kolibri's telemetry server, actually. It might be able to choose not to send these particular notifications to this particular client.
I have the following version of this Flatpak installed:
(Note Version: 1.0 which I think applies to the kolibri-installer-gnome version number – the version of Kolibri itself is Kolibri 0.13.3a0.dev0+git.62.g5d05c61b.)
Whenever I start the app and log in (grr), I get the following prompt:
As a user of the Flatpak, I can't take action based on this notification. At a minimum, the Flatpak package should disable Kolibri's update check.
Ideally, kolibri-installer-gnome would detect that it is within a Flatpak and use the Flatpak UpdateMonitor API to detect when an update is available and prompt the user to apply the update and restart the app.