You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Before Submitting: Double-check that you are running the latest version of the plugin. The bug might have already been fixed 😄
Describe the bug
A fetch of 0 tasks updates the sync time (this is fine if there are no tasks).
A failed access (maybe on iOS) returns 0 tasks fetched.
After one failed call (this might be a call on winOS or iOS) the sync time (this.options.latestSyncTime) will be set to the active timestamp and new syncs will not fetch any old tasks.
Describe the bug
A fetch of 0 tasks updates the sync time (this is fine if there are no tasks).
A failed access (maybe on iOS) returns 0 tasks fetched.
After one failed call (this might be a call on winOS or iOS) the sync time (
this.options.latestSyncTime
) will be set to the active timestamp and new syncs will not fetch any old tasks.This comes from here:
Steps to reproduce
I fixed my problem by a hard reset of the
latestSyncTime
, replacing the initialisation oflatestSyncTime
And reinserting the correct code afterwards.
Expected behavior
Environment (please specify)
OS
macOS
Obsidian Version (e.g. v0.10.6)
The text was updated successfully, but these errors were encountered: