Alright, folks, it’s been another few weeks, and it’s time for another Sparkle release! You can grab it here. I’m frozen on new code now, and there are no known bugs left, so unless there’s something critically wrong, this’ll be the last beta before 1.5 final.
Another piece of good news is that Sparkle’s documentation is finally coming together, and in wiki form. Check it out, and feel free to contribute.
Make sure you read the release notes thoroughly; the important thing to note is that DSA signatures are now required.
I could really use help from localizers on the remaining languages! If you are or know a localizer for a language Sparkle’s missing, please let me know.
Sparkle 1.5b6 Release Notes
- Sparkle now requires DSA signatures on your updates. Check the documentation for more information on how to set that up if you don’t already sign your updates. You can bypass this requirement if you deliver both your appcast and your updates over SSL.
- Sparkle will no longer display release notes located at file:// URLs, since Javascript on such a page would be able to read files on your file system.
- For security reasons, Sparkle will refuse to install updates which appear to “downgrade” the app.
- SUUpdater now implements new keys: “automaticallyDownloadsUpdates”, “lastUpdateCheckDate”, and “sendsSystemProfile.”
- Fixed a bug that could prevent SUProbingUpdateDriver from working.
- Fixed a bug that prevented the updaterWillRelaunchApplication: delegate method from getting called.
- Fixed displaying release notes transmitted “loose” in the <description> key.
- Fixed Sparkle compilation on 10.4 systems.
- Fixed a bug that could cause window confusion if an app changed its LSUIElement at runtime.
- Added support for Sparkle 1.1’s behavior of disabling updates when the check interval is 0.
- Sparkle can now handle appending parameters to URLs which already have parameters.
- If an update’s sparkle:shortVersionString is the same as the host’s CFBundleShortVersionString, the sparkle:version and CFBundleVersion will be presented in parentheticals.
The Conversation {7 comments}
“no known bugs”
famous last words?
“Known”! “Known”!
:D
Maybe it’s just me going crazy trying to get update signing to work, but I’m getting:
Sparkle Error: No valid unarchiver for /var/folders/Ye/YeN8ZCSj2RW+-E+8ZRIVJ++++TI/-Tmp-/Transmission 1 Update 17/Transmission-1.33.dmg.bz2!
Sparkle Error: An error occurred while extracting the archive. Please try again later.
Mind you, it’s a .dmg I’m downloading, not a .dmg.bz.
Mitch, this is not a signing problem. The problem is that the mirror does not report the (correct) mime type of the downloaded file. This seems to be happening a lot in particular with Transmission. The download mechanism will then add a file extension based on its best guess. As a .dmg apparently contains bz2 compressed data (looking at the first few bytes of the data), it decides it should have a .bz2 extension. The real fix for this is that the servers should report the correct mime type (application/x-apple-diskimage).
However, as this particular one seems to be somewhat common, I think Sparkle could second-guess the default file name in certain cases (e.g. when the reported MIME type is missing or generic, and the file extension of the URL and the suggested file name are different).
hi
i always get “Update Error!” when i’ve downloaded the file and click “Install and Relaunch”. is there a problem with the signing?
Maybe! Check the console for more info.
Hello,
I would like to mention that the Monobjc bridge project now support the Sparkle update engine.
Monobjc is .NET/Objective-C bridge that allows .NET application to use the Mac OS X framework like Cocoa or Webkit in a transparent manner.
For more information, check out http://www.monobjc.net/
Regards, Laurent Etiemble
Leave a Comment
You can follow any responses to this entry via its RSS comments feed. You can also leave a trackback if the inclination is there.