Keep a database handle when the File Provider domain is unusable (fix post-update sign-in)

[alexmodrono]

Summary

Signing in right after a Sparkle update failed with "Database error: database not available". A normal relaunch worked.

Root cause (confirmed from app logs): after Sparkle replaces the bundle, macOS temporarily disables the File Provider extension. On that first launch NSFileProviderManager.stateDirectoryURL() throws, and that throw propagated out of configureInitialDatabase, so database was left nil — loadAccounts bailed (no session), and persistSignIn threw "Database not available". On a later manual relaunch the extension is re-enabled, so it worked.

Fix

configureInitialDatabase now always opens the App Group bootstrap database first (it doesn't depend on the File Provider domain), then tries to upgrade to the shared state-directory database. So the app always has a working handle; the session bootstrap re-seeds + adopts the shared DB once the extension is back. persistSignIn also opens a bootstrap handle if none is active, as a backstop.

This is a pre-existing fragility in the original 0.2.0 code. Note: the 35→36 update itself exercises the fix (the post-update launch runs build 36's code).

Build

Compiles clean.

[github-actions]

Nightly Build

Download Findle Nightly (unsigned)

Built from 17d0bfc.

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.