Skip to content

OmniDrive 1.1.0

Latest
Latest

Choose a tag to compare

View all tags
@Chubbyy Chubbyy released this 27 Sep 21:56
1.1.0
f108beb

OmniDrive 1.1.0

This release focuses primarily on reliability, security, and hardening sync capabilities.

It is recommended that vaults are backed up prior to updating just in case. Thorough testing was conducted before this update, but unforeseen issues may still persist.

Highlights

  • Secure credential storage

    • Google client secrets and refresh tokens are now stored using Obsidian SecretStorage.
    • Existing plaintext credentials are migrated automatically and are only removed from data.json after secure-storage verification succeeds.
    • Normal sync/index/settings saves no longer depend on SecretStorage availability.
    • New devices may require the client secret to be re-entered and Google authentication to be completed again.

  • Safer Google Drive communication

    • Transient Drive GET failures now use bounded retries for rate limits and common temporary server/network failures.
    • Writes and OAuth requests are not automatically replayed.
    • Rate-limit-specific 403 responses are distinguished from permission failures.

  • More reliable Drive discovery

    • RADAR and folder discovery now support pagination with up to 1,000 results per page.
    • Repeated continuation tokens are detected instead of looping indefinitely.
    • OmniDrive-marked folders are preferred, while ambiguous folder lookups now fail safely instead of selecting an arbitrary folder.

  • Improved rename and index handling

    • Cloud-driven rename echoes are suppressed more precisely.
    • Folder renames immediately cascade tracking changes to descendants.
    • Several reconciliation paths now use safer reverse-index handling.

  • Improved sync failure reporting

    • Failed file operations no longer result in a false successful-sync message.
    • Queue failures remain isolated so other files can continue syncing.
    • Successful syncs are recorded in debug logging.

  • Large attachment upload hardening

    • Resumable uploads now use explicit binary upload metadata and safer request headers.
    • Initialization and individual chunk failures produce more useful diagnostics without exposing resumable-session URLs.
    • Interrupted sessions are not persisted across Obsidian restarts; a later sync may begin a new resumable session or safely re-link an already completed Drive copy.

  • Safer rebuild behavior

    • Rebuild Index verifies authentication and the selected remote vault before clearing tracking state.
    • A valid selected remote vault is preserved rather than unnecessarily replaced.

Improvements

  • More robust local-file read retries.
  • Better handling of missing file extensions.
  • Remote-vault selection and folder-setup callbacks now handle rejected asynchronous operations.
  • Documentation for One-Way Backup, Historic Archive, credential storage, and resumable uploads has been clarified.
  • Expanded automated regression coverage for syncing, credentials, retries, folder discovery, pagination, and reconciliation.

Known limitations / Future Considerations

The following remain intentionally deferred for future updates:

  • Full-crawl duplicate local-path collision detection.
  • Crash-atomic index rebuilds.
  • Persisted resumable-upload sessions.
  • Narrower Google OAuth authorization.
  • Google Drive Changes API support.
  • Greater internal main.ts decomposition.

Please report any bugs or request features from the plugin's listing: https://community.obsidian.md/plugins/omnidrive

Thank you!

Assets 5
Loading