Bug Description
This is a very weird bug. It only happens with a certain file, which unfortunately I use every day. So to me it's very important to solve. I post here because I'm at wit's end how to fix it.
- The file contains several Bases views with lists of exercises in it.
- If I click on one of those exercises in the view, this of course takes me to the exercises.
- But, when I then use the back arrow in the upper left corner of the file, Obsidian hangs and I have to restart Obsidian.
- This is only true for the back arrow in the upper left corner.
- The one in the virtual keypad that shows up in the bottom does not cause the hang.

Why I "blame" TaskNotes at the moment
- This only happens if TaskNotes is enabled.
- If TaskNotes is disabled, it never happens, regardless of other plugins being enabled.
Why this is hard to debug
- This is only true for this list of exercises.
- Other files containing view do not seem to exhibit this bug.
- It makes me think there is a corrupt cache or something related to this file.
- However:
- There is no sandbox vault on iPad so I can't test with that.
- This only happens on my iPad, not the same file on my MacBook.
- On Obsidian on iPad, there are very limited tools to inspect what is happening.
What I'm asking
How can I resolve this please? :-)
I fear because of the specificity I can't even give you a reproducer. I'm hoping maybe you can give me some ideas of how to give you better information for debugging.
Current workaround
- If I only use the arrow shown in the image above, the bug is not happening, so hopefully I can remember to do that every time for this file.
- I often forget. :-)
Bug Description
This is a very weird bug. It only happens with a certain file, which unfortunately I use every day. So to me it's very important to solve. I post here because I'm at wit's end how to fix it.
Why I "blame" TaskNotes at the moment
Why this is hard to debug
What I'm asking
How can I resolve this please? :-)
I fear because of the specificity I can't even give you a reproducer. I'm hoping maybe you can give me some ideas of how to give you better information for debugging.
Current workaround