How to detect if an update is available #2604
-
I would like to add a small badge/button in my app's UI when a software update is available. When the user clicks on it, Sparkle's standard update UI (with release notes) should appear. I'm probably missing something very basic, but I'm not sure how my app should check whether an update is available without also making the Sparkle's UI appear. I'd love to simply have a |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 3 replies
-
https://sparkle-project.org/documentation/gentle-reminders/ is designed to handle this use case. By default Sparkle handles scheduling update checks periodically (this is orthogonal to not showing the full UI actually). Gentle reminders is for overriding the presentation of the new update behavior when an update check is performed and a new update is available to be shown. In the older days, some apps would do two update checks; one "silent background info" update check to see if a new update was available, then another update check when the user hits the badge. I don't recommend this approach because it's inefficient. |
Beta Was this translation helpful? Give feedback.
-
Ok, I've got the gentle reminders working, and it seems like its purpose is to make only the scheduled update checks happen in a gentle/no-UI way. My implementation creates an I discovered that I can do this by running the SPUUpdater's I just wanted to check this solution with you, in case I misunderstood something. Thanks! |
Beta Was this translation helpful? Give feedback.
https://sparkle-project.org/documentation/gentle-reminders/ is designed to handle this use case.
By default Sparkle handles scheduling update checks periodically (this is orthogonal to not showing the full UI actually). Gentle reminders is for overriding the presentation of the new update behavior when an update check is performed and a new update is available to be shown.
In the older days, some apps would do two update checks; one "silent background info" update check to see if a new update was available, then another update check when the user hits the badge. I don't recommend this approach because it's inefficient.