Skip to content

fix: keep Sparkle off the cold-start URL path - #6

Merged
TerrifiedBug merged 1 commit into
mainfrom
fix/sparkle-off-hot-path
Aug 27, 2026
Merged

fix: keep Sparkle off the cold-start URL path#6
TerrifiedBug merged 1 commit into
mainfrom
fix/sparkle-off-hot-path

Conversation

@TerrifiedBug

Copy link
Copy Markdown
Owner

makeUpdater() ran as an AppDelegate stored-property initializer, so SecStaticCodeCheckValidity hashed the whole bundle (including Sparkle.framework) before a cold-start URL open was dispatched.

  • Construct the updater on the next main-actor turn after applicationDidFinishLaunching, once the status item exists. AppServices.updater stays the no-op until then.
  • Pass kSecCSDoNotValidateResources. The Developer ID requirement (team 92X3ACDPD2, leaf OID 6.1.13) still fails ad-hoc and Apple Development.

This should land before the first v* tag.

makeUpdater ran as an AppDelegate stored-property initializer, so
SecStaticCodeCheckValidity hashed the bundle (including Sparkle)
before the first open URL was dispatched. Construct the updater on
the next main-actor turn after launch, and skip sealed-resource
hashing; the Developer ID requirement still rejects ad-hoc builds.
@TerrifiedBug
TerrifiedBug merged commit d21cb05 into main Aug 27, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant