This is meant to increase the success of downloaded updates from finishing installing on system shutdown. The updater progress app needs to use dispatch source for observing when the PID dies because LaunchServices may no longer be available at this point.
Before an update is superceded we will need to send a skip/cancel message to expedite the termination of the helpers.
The user can rename the host bundle filename so it's not reliable and gives a false sense of reliability. We keep matching against the name of the bundle derived from the Info.plist and the bundle identifier.
This fixes a regression introduced in Sparkle 2.9 when signed feeds were added. In our documentation we have suggested surrounding the release notes URL with newline/whitespace for pretty-print formatting reasons. However now that this bug surfaced, the documentation will be updated to remove the extraneous whitespace. Many developers generating appcasts programmatically or with generate_appcast will not run into this issue.
* Changed Update Permission Prompt to resemble Tahoe Alert
* Simplified layout code and cleaned up the xib for Interface Builder
* Fixed checkbox alignment in right to left languages
---------
Co-authored-by: Anderson4366 <neo.volkmann@icloud.com>
The update cycle is refactored and simplified. Notably we remove a suite of classes (automatic, probe, UI scheduled, UI initiated, core, basic, more..) and collapse them into a single update driver. If the update driver is started in automatic mode, it can escalate into UI mode without ending the cycle (previously we would end the cycle and flag that the next cycle had to be started in a UI mode carrying the previous update). SPUUpdater doesn't do installer progress queries anymore and thus these have been reduced.
Even if a prior update has been downloaded before, the updater uses the regular scheduled check interval and the update driver is responsible for determining whether or not the impatient update interval has elapsed. Every update check checks if a newer superseded update is available and if it should replace any updates that have been previously been downloaded or started installing.
The two conditions we do not check for superseded updates is if the installer is ran in the system domain (requiring authorization), and updating other bundles from an external updater (to not conflict with apps self-updating themselves).
This change adds a UI test to test a superseded update is downloaded and began to install automatically.
Fixes#2469. Previous attempt was in #2908 but I decided that was hacking the current architecture too much and exposing issues making it hard to implement this functionality correctly. Used AI for much of this refactoring, reviewing, and code implementation.
When an existing item's description is rewritten with HTML release notes,
the sparkle:format attribute from a previous plain-text or markdown
description was kept, so Sparkle kept rendering the new HTML as that format.
The guard compared the directory name (e.g. "en.lproj") against "en" and
"Base", so it never matched and both locales were recorded in
sparkle:deltaFromSparkleLocales, taking up slots of the 7 sampled locales.
Compare the locale name after dropping the .lproj extension instead.
The children of <sparkle:informationalUpdate> and <sparkle:tags> were matched
against their qualified name instead of being resolved through the Sparkle
namespace URI, unlike every other element in the parser.
If the user initiated update check performs fast enough, we won't show the check for updates progress status window, and transition right away to the new update / update not found / update error occurred windows.
Orthography, and a few errors that changed what the strings said.
The spelling is pre-1990 Orthographic Agreement, which Portugal adopted in 2009
and has used in official and technical writing since 2015: "actualização" is now
"atualização". Every occurrence, 13 strings.
Beyond spelling:
· "Ocorrer um erro ao processar o feed" — infinitive where the preterite
belongs; the other three error strings say "Ocorreu".
· "Por favor novamente tente mais tarde" — wrong word order, in two strings.
The other two in the same file already say "tente novamente".
· "está dísponível" — stray accent.
· The ready-to-install prompt asked whether to install now and relaunch
"posteriormente" (later). The English asks to relaunch now, and the button
says "Instalar e reiniciar", so the question contradicted both.
· "%1$@ can't be updated because it was opened from a read-only or a temporary
location" still had the older wording it replaced, describing disk images and
optical discs. It now says what the English says.
· "procurar por atualizações" — anglicism; the rest of the file already says
"procurar atualizações".
· In the system-profile disclosure, "future" qualifies the development work,
not the helping: "para nos ajudar a planear o trabalho de desenvolvimento
futuro".
All 38 keys, their order, and every format specifier are unchanged.
---------
Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
Co-authored-by: Zorg <zorgiepoo@gmail.com>
* Add more test cases for extracting licensed disk images
* Revert "Unarchive disk images using diskutil on macOS 27+ (#2902)"
This reverts commit 91ac4bbe81.
This change adopts using diskutil for dmg extraction on macOS 27+ where hdiutil has been deprecated. hdiutil will still be used on older operating systems because diskutil's extraction support is worse prior to macOS 27 (e.g. can't handle license agreements in headless way, stricter --mountPoint policy requiring mount directory to exist).
As part of this change, SUStatus window is now being created programmatically rather than from a nib, so the nib does not need to be loaded in the progress tool (Updater.app) nor duplicated. The localizations this helper tool needs are also now being autogenerated. In the Updater.app, since the app can be swapped, we will minimize what needs to be loaded from disk. Also, the progress Updater app is no longer brought up the from when its status window shows, which could cause it to show up as a recent app entry in the Dock.
I used AI to re-generate the SUStatus window programmatically, which I've verified have same properties as the removed xib, and to create the python script to generate the localization header for the Updater app which I've reviewed.