I recently updated and also moved my notes storage, and due to one, the other, or both of these I seem to no longer be able to create or read notes. When opening the app, I see a call stack error in the console and any storage I had previously configured will now be gone:
After adding the storage folder again, I still cannot add a note (I receive the 'no storage to create note' warning message, though it is not pictured):
Even though the storage list still contains the newly added location:
Closing and reopening the application starts the process over again: stack error, missing storage folders, so on.
Hmm.. How can I reproduce this problem?
Good question. A bunch of fiddling/uninstalling/reinstalling never got me back to a working state. However, one of the error traces pointed me here: https://github.com/substack/node-mkdirp/issues/126, which sounds a lot like my edge case (as I mentioned, I just finished moving my notes location, and it did involve a volume change)
Following that, to repro, I did the following:
So looks like it's a good old dependency issue.
Also worth noting that order to get boostnote working at all again, I had to uninstall, completely remove the .../AppData/Roaming/Boostnote directory, and reinstall. I'm not sure what in there is persisting the old volume info, but something seems to be.
I see. Boostnote store volume info to LocalStorage. Hmm.. I think we have to handle the error.
I had the same issue. Workaround:
After restart all should be work as expected. But note that your settings will be lost!
I had the same issue. Workaround:
- Open Developer Tools (View -> Toggle Developer Tools)
- Switch to Application Tab
- Extend Local Storage
- Right Mouse Click on file:// and press Clear
After restart all should be work as expected. But note that your settings will be lost!
This finally worked for me, thank you.
It works for me too . Thanks @marcelbraun1985 :) !
I think this issue is no longer present in the latest version.
If you still are experiencing this problem then feel free to reopen this issue or create a new issue with all the relevant information.
Most helpful comment
I had the same issue. Workaround:
After restart all should be work as expected. But note that your settings will be lost!