1.0.51
18th November, 2026
Fixed
-
Files registered as Ignore or Automatic in Customisation sync no longer trigger new snapshots during configuration scans. (#1359)
- Existing snapshots are retained. Exclusions still rely on each item's recorded file list, and this fix does not repair empty or outdated lists.
-
Hidden File Sync now respects Customisation sync exclusions (Ignore and Selective) for registered paths containing uppercase letters. (#1359)
- When Customisation sync is enabled, the exclusion check compares both paths in lowercase, restoring case-insensitive matching.
Improved
-
We can see at a glance when automatic synchronisation is disabled, including while it remains suspended after Fetch or Rebuild. (#1361)
- A framed badge in the status bar and editor overlay displays the configured LiveSync, Periodic, On events, or manual-only mode alongside current transfer activity.
- Available for CouchDB and S3-compatible Object Storage remotes. Fetch and Rebuild retain their existing suspension behaviour.
-
We can mute recurring plug-in version Notices for individual devices from Joined devices using Mute version notices. (#1349, #1368)
- Choices are retained only for this Vault on this device and can be reversed with Unmute version notices, while synchronisation compatibility checks remain enabled. Removing a device record remains available under … → Forget device record….
Recovery work in progress
-
This plug-in can now reopen an unavailable local database before resuming synchronisation, after a read against the current connection fails, instead of requiring an immediate force-quit. (#1360)
- Local file dispatch is held while the connection is replaced; if reopening fails, this plug-in requests an Obsidian restart. This recovery path does not prevent platform disconnections or detect an adapter operation which never settles.
- Controlled Linux Obsidian recovery tests pass; natural background connection loss and recovery on a physical iPhone remain unverified.
-
Ordinary Vault files which could not be reflected are retained for recovery and review, rather than remaining silently unapplied until another scan. (#1224, #1360)
- Failures at known local database or remote content-read boundaries are eligible for one automatic retry after every required resource recovers. Failures without an established retry condition and items whose automatic allowance is exhausted remain available under Hatch → Recovery and Repair → Review files which could not be reflected.
- Native request failures preserve their origin without relying on message text, and reopening the same local database retains saved recovery items and consumed retry allowances.
Developer tools
- The Review Harness (enabled via Power users → Enable Developers' Debug Tools) adds individual database diagnostics: Database connection-loss diagnostic, Database background-events diagnostic, and Database transaction-abort diagnostic.
- These diagnostics use disposable database fixtures and record observations only; a run with no observed failure does not establish that recovery succeeded or attempt automatic product recovery.
CLI
Fixed
- CLI file lookups avoid full Vault scans when checking files which have not arrived locally or have already been deleted. (#1347)
- With Legacy file identity (
pathNormalizationVersion: 0) and case-insensitive file-name handling, matching directory branches are listed directly instead of scanning unrelated Vault subtrees.
- With Legacy file identity (
Docker
Fixed
- The Docker Compose sample can now re-run initialisation against an already configured CouchDB server and preserve authentication and CORS settings when the container is recreated. (#1356)
- The initialisation check authenticates with CouchDB, and a dedicated volume retains runtime configuration. Before recreating CouchDB on an existing stack, save and transfer its settings as described in Data & Backup.
Miscellaneous
- Updated dependencies (including
@vrtmrz/livesync-commonlib0.6.0).
Acknowledgements
Thank you for your contributions!