-
-
Notifications
You must be signed in to change notification settings - Fork 6
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
Only first load / update works, Update button fails & requires restart #18
Comments
Sorry for the late reply. Do you still have this issue now after adding some tasks and labels to your Marvin? I've tried to replicate but I could not reproduce the issue, can you walk me through your settings on Marvin? |
I also experience this issue as described - it works once, but once the refresh button is clicked it then requires a restart of Obsidian. I tried changing plugin settings as described in step 6, but that didn't unblock the plugin. The only thing that worked for me was restarting the application. |
@ultron did you ever work around this issue, or find another way to hook AM into Obsidian? Thanks |
@edhilgendorf Alas no. I like both AM and Obsidian a lot, but they don't play nice together. |
Does yours ever show daily items? I can see master list but no tasks ever load. Thinking about forking this and giving it a shot.. |
Hi all,
many thanks for this plugin. It makes me consider switching from Roam to Obsidian, simply to get Task interop with Marving.
As such, I just installed a fresh version of Obsidian, using an empty vault. I have Sync enabled (but also tried with it disabled).
The issue is the same when I add today or due-today notes to any other open file.
So in conclusion, the "Update" Button leads to the the AmazingMarvin sync to become stuck across Obsidian, requiring a restart. My experiments seems to indicate that it is literally the button itself that is the issue, not the API or repeated calls to the API.
What can I do to help with this issue? Any files you would like me to supply? Any tests to run?
The text was updated successfully, but these errors were encountered: