Skip to content

Fix File Provider re-registration and WhatsNewKit version#11

Merged
alexmodrono merged 1 commit intomainfrom
worktree-release-0.1
Mar 18, 2026
Merged

Fix File Provider re-registration and WhatsNewKit version#11
alexmodrono merged 1 commit intomainfrom
worktree-release-0.1

Conversation

@alexmodrono
Copy link
Copy Markdown
Owner

Summary

  • Re-register File Provider domain after app updates to fix "signed out" and permission errors
  • Fix WhatsNewKit version to match actual release (0.1.2, not 1.0.0)

…updates

WhatsNewKit: The WhatsNew entry had version "1.0.0" but the production
app ships as 0.1.x, so the sheet never triggered.  Changed to "0.1.2"
to match the actual release version.

File Provider: After a Sparkle update the embedded extension binary
changes but fileproviderd keeps a stale reference to the old one,
causing "signed out" and "does not have permission" errors.  The app
now tracks its build number across launches and, when a version change
is detected, removes and re-adds the File Provider domain to force
macOS to reload the extension.  The shared database is preserved via
a bootstrap snapshot/re-seed cycle.
@alexmodrono alexmodrono merged commit 454c04b into main Mar 18, 2026
1 check passed
@github-actions
Copy link
Copy Markdown

Nightly Build

Download Findle Nightly (unsigned)

Built from 929e794.

Important

This build is unsigned. macOS will block it on first launch. To open it:

  1. Try to open the app normally — macOS will show a warning and refuse.
  2. Go to System Settings → Privacy & Security, scroll down, and click Open Anyway.
  3. The File Provider extension requires code signing and won't work in this build.

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