Autoupdate of macOS app via Sparkle library fails

We have a macOS app distributed outside of the Mac App Store (Developer ID distribution). It incorporates the popular Sparkle library which offers autoupdate functionality (downloading and installing new versions of the app).
The autoupdate functionality worked flawlessly for many years but with recent versions of macOS it started failing.

To demonstrate the problem we offer the dts-demo.tar.gz file (available for download, see the links below). That file contains the sources of DemoApp and a build_packages.sh script that builds installer packages for two versions of DemoApp. The old version is 3.0 and the new version is 4.0. Manually installing the old version (by double-clicking the .pkg file and following the instructions) succeeds. After launching the app, trying to autoupdate to the new version by clicking the "Check for update" button fails. The process starts, the old version is deinstalled but then the installation of the new version fails. Manually installing the new version of the app over the old version succeeds.

The problem has been observed on macOS versions after 26.6.2 (e.g. 26.7.3 or 27.0).

The files we offer for download are:
dts-demo.tar.gz at https://dx4vjdxzj60n5.cloudfront.net/dts-demo.tar.gz
manual_install_v3.log at https://dx4vjdxzj60n5.cloudfront.net/manual_install_v3.log
autoupdate_to_v4.log at https://dx4vjdxzj60n5.cloudfront.net/autoupdate_to_v4.log
manual_install_v4_over_v3.log at https://dx4vjdxzj60n5.cloudfront.net/manual_install_v4_over_v3.log

The provided log files are excerpts from the system's install.log file.

The Sparkle framework included in dts-demo.tar.gz comes from the official Sparkle 2.10.1 release. That version is the latest available at the time of writing. Please note that it only accepts URLs with 'http' or 'https' schemes.

This autoupdate problem looks like a bug in macOS because manual updates succeed. We'd like to have the bug fixed or at least find a workaround.

Thanks for the post. I like sparkle but I would recommend to check with that 3rd party tool.

A few suggestions when you said that manual install works, but autoupdate fails after the old version is removed points to the installer is running in a different state than in the manual case? Looking at the logs you provided, it seems like is pointing to localhost?

2026-11-11 23:02:51+02 stest27d installer[825]: -[IFDInstallController(Private) _buildInstallPlanReturningError:]: location = file://localhost
2026-11-11 23:02:51+02 stest27d installer[825]: -[IFDInstallController(Private) _buildInstallPlanReturningError:]: file://localhost/var/root/Library/Caches/com.example.DemoApp/org.sparkle-project.Sparkle/Installation/3xweeA14R/GjsOXKZsE/A9FC88BD-0450-4A0C-8A88-E382ECDC6983.pkg#com.example.DemoApp.pkg
2026-11-11 23:02:51+02 stest27d installer[825]: -[IFDInstallController(Private) _buildInstallPlanReturningError:]: file://localhost/var/root/Library/Caches/com.example.DemoApp/org.sparkle-project.Sparkle/Installation/3xweeA14R/GjsOXKZsE

Also looks like a directory issue in permissions updating?

2026-11-11 23:02:52+02 stest27d installd[688]: PackageKit: Failed to unlinkat file reference /Library/Filesystems/DemoBundle.bundle/Contents/Info.plist, error: Operation not permitted

Sparkle doesn't uninstall anything for package updates. If a preinstall script deletes the old app, that script is probably what is failing or changing state?

Albert  WWDR

There is no preinstall script involved. Look at the contents of dts-demo.tar.gz. It contains everything necessary for reproduction.

What fails is the shove step and shove is a part of the private PackageKit framework, which is supplied by Apple. Also, permissions checking is performed by the kernel and various system daemons, also supplied by Apple.

@JordanW1 Thanks if there is no script that deletes the old app. Can you gather those logs and submit a bug for that team so they can review them to see if there is an issue in macOS 27?

Once you open the bug report, please post the FB number here for my reference.

If you have any questions about filing a bug report, take a look at
Bug Reporting: How and Why?

Albert  WWDR