Installing the update using the dmg package gives an error: "XPC_ERROR_CONNECTION_INTERRUPTED"

[soulcure]

dmg package not work:

zip package works fine:

Description of the problem

• Installing the update using the zip package works fine.
• Installing the update using the dmg package gives an error: "Re-initialization successful; calling out to event handler with XPC_ERROR_CONNECTION_INTERRUPTED"

Do you use Sandboxing in your app?

<key>com.apple.security.app-sandbox</key>
<false>

Version of Sparkle.framework in the latest version of your app

Sparkle (2.7.1)

Version of Sparkle.framework in the old version of app that your users have (or N/A)

NO

Sparkle's output from Console.app

默认 16:54:47.570957+0800	ARZOPA	[0x1454722f0] activating connection: mach=false listener=false peer=false name=org.sparkle-project.InstallerLauncher
默认	16:54:47.578603+0800	ARZOPA	[0x1454722f0] Re-initialization successful; calling out to event handler with XPC_ERROR_CONNECTION_INTERRUPTED
默认	16:54:47.578639+0800	ARZOPA	[0x1454722f0] invalidated because the current process cancelled the connection by calling xpc_connection_cancel()

Steps to reproduce the behavior

appcast.xml

<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:sparkle="http://www.andymatuschak.org/xml-namespaces/sparkle">
  <channel>
    <title>Arzopa</title>
    <description>Arzopa 桌面应用程序更新源</description>
    <language>zh</language>
    <item>
      <title>Version 1.0.3</title>
      <sparkle:version>100003</sparkle:version>
      <sparkle:shortVersionString>1.0.3</sparkle:shortVersionString>
      <pubDate>2025-08-29</pubDate>
      <enclosure url="https://app.arzopa.cn/montior/ARZOPA-1.0.3-macOS.zip"
          sparkle:edSignature="LKWPO5gHjvvvDSxXmITCzIwszLQPBDxHL8+3V7LvBXQiWIYBTmiLyRsKLo+qC9R9N+4JGlKUYWl0R6TqlLGQCw=="
          sparkle:os="macos"
          length="27418225"
          type="application/octet-stream" />
    </item>
  </channel>
</rss>

Release.entitlements

<!-- Sparkle 更新器所需权限 -->
<key>com.apple.security.automation.apple-events</key>
<true/>

<!-- 允许 Sparkle 安装器服务 -->
<key>com.apple.security.temporary-exception.mach-lookup.global-name</key>
<array>
	<string>com.apple.installer.installer</string>
	<string>com.apple.installer.installer.helper</string>
</array>

[zorgiepoo]

[0x1454722f0] activating connection: mach=false listener=false peer=false name=org.sparkle-project.InstallerLauncher

If your app is not sandboxed, you should not enable the InstallerLauncher service (do not use SUEnableInstallerLauncherService)

Likely there should be more logs for your app about the error, or under the Autoupdate process (and less likely the Updater process). This is most likely a configuration issue.

The appcast.xml file you pasted was for your "working" zip package, not the dmg version. As a wild guess that could mean your dmg was not correctly signed with the correct edSignature. If you code sign or staple (as part of notarization) your dmg file, you will need to do that before generating the edSignature because that modifies the disk image file. Again if this is the issue, there should be more logs.

[zorgiepoo]

Ah, didn't realize the error message was about not connecting to the installer. It's weird that dmg vs zip would make a difference there (it shouldn't). In addition to checking the logs for Updater and Autoupdate processes, and making sure you're not using InstallerLauncher service for a non-sandboxed app, I'd also check if there are any relevant crash logs in Console app under Crash Reports.

You could also upload an affected build and I could take a look.

[soulcure]

Why does Installer.xpc not have execution permissions when using DMG packaging?

When using the zip packaging method, Installer.xpc has execution permissions

[zorgiepoo]

That is an issue with how you are making your app bundle (and copying Sparkle) or how you are creating your disk image (and not preserving permissions). It's not a Sparkle issue. Other apps don't package Sparkle incorrectly in disk images.

Like I said earlier, you also shouldn't use the Installer XPC Service if your app isn't sandboxed. But you need to also make sure the executable-bit is not missing with other helper executables in Sparkle.framework like Autoupdate or Updater.app

[soulcure]

I changed the Installer permission to 755 in the dmg script, and I was able to upgrade and install the dmg.
or Can I still open the sandbox directly and upgrade using the dmg method?

[zorgiepoo]

Sparkle supports dmg in a sandboxed environment.

Changing the permission is a hack and is hiding the issue. You need to actually figure out what in your setup is losing the permission bit and fix that. Certain tools like cp or zip for instance can lose the permission bit if you don’t provide necessary flags (in those cases, ditto should be use instead).