For example, if 2.0 is a major release offered and the user is on 1.9.4, they can choose to skip 2.0 and its future minor updates (eg 2.1). A user can choose to skip out of future update alerts to a major upgrade.For example, if 2.0 is marked as a major release (with sparkle:minimumAutoupdateVersion set to 2.0), but 1.9.4 is available then 1.9.4 will be offered first. A developer can publish a new minor patch release preceding the major release and Sparkle will prefer to install the latest minor release available.Apps with a lower CFBundleVersion will always see the update available GUI, regardless of their SUAutomaticallyUpdate user defaults setting. without showing the update available GUI). If this value is set, it indicates the lowest version that can automatically update to the version referenced by the appcast (i.e. Version 2.1 (2 bugs fixed 3 new features) 2.1 2.0 If an update to your application is a major or paid upgrade, you may want to prevent the update from being installed automatically.Īdd a sparkle:minimumAutoupdateVersion child to the in question specifying the major update’s, such as “2.0”: To minimize issues, we recommend building your application with an up to date Xcode and SDK.Īdditionally in Sparkle 2, if the user checks for new updates manually and the cannot update because of an operating system requirement, the standard updater alert will inform the user their operating system is incompatible and provide them an option to visit your website specified by the element. Please note that if your application is built using the macOS 10.15 SDK or earlier, the system may report its operating system as 10.16.0 for compatibility reasons. Sparkle also supports a sparkle:maximumSystemVersion element that can limit the maximum system version similarly. Note that Sparkle 2.3 or later only works with macOS 10.13 or later (macOS 10.11 or later for Sparkle 2.2.2 and macOS 10.9 or later for Sparkle 1), so that’s the lowest minimum version you can use. Version 2.0 (2 bugs fixed 3 new features) 2.0 10.13.0 If an update to your application raises the required version of macOS, you can restrict that update to qualified users.Īdd a sparkle:minimumSystemVersion child to the in question specifying the required system version, such as “10.13.0” (be sure to specify a three-part version in form of ): Note that the internal version number ( CFBundleVersion and sparkle:version) is intended to be machine-readable and is not generally suitable for formatted text or git changeset IDs. Then set a sparkle:shortVersionString element on in your item to the human-readable version (ie: “1.5.1”). Set the sparkle:version element in your item to the internal, machine-readable version (ie: “1248”). If you use internal build numbers for your CFBundleVersion key and a human-readable CFBundleShortVersionString, you can make Sparkle hide the internal version from your users. The generate_appcast tool automatically generates delta updates. If your app is large, or if you’re updating primarily only a small part of it, you may find delta updates useful: they allow your users to only download the bits that have changed. This is supported across all versions of Sparkle. While this works fine, for overall consistency we now recommend specifying them as top level items instead as shown here. Note on sparkle:version: Our previous documentation used to recommend specifying sparkle:version (and sparkle:shortVersionString) as part of the enclosure item. Version 2.0 (2 bugs fixed 3 new features) 2.0
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |