-
-
Notifications
You must be signed in to change notification settings - Fork 55
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] In obsidian 1.7.4, sync errors prevents app from starting #301
Comments
Okay, I let the load process run out for longer, and I found that there is a sync error in console for what appears to be every single book. This appears to be a bug with syncing that is triggered at obsidian start up by enabling "Sync at Startup". After rerunning the manual sync a few times, these errors went away (despite reloading obsidian half a dozen times and getting the same errors). I'm not sure if this is due to the plugin somehow marking these as failed and giving up, or if rerunning it a bunch of times managed to jostle something into place and fix it. Either way, this error/bug has stopped for me, at least for now Sync error: |
I have the same issue |
Ditto, still. So just keep disabling and re-enabling until it stops? |
I had this issue, disabled the plugin during the load. After Obsidian loaded, I reenabled the plugin, then went to Kindle Highlights settings, and disabled "Sync at Startup". That seemed to fix the issue. |
Describe the bug
in Obsidian 1.7.4, the new startup load time optimization feature flags this plugin at start up as "taking a long time to load" and offers the option to disable this plugin. Unless you disable the plugin, Obsidian will never load at startup.
The plugin loads and seems to operate fine (i.e. with no new bugs) if manually enabled after startup.
Method of syncing
To Reproduce
Steps to reproduce the behaviour:
Expected behaviour
Vault should be loadable with this plugin enabled
Screenshots
If applicable, add screenshots to help explain your problem.
Metadata
The text was updated successfully, but these errors were encountered: