-
Notifications
You must be signed in to change notification settings - Fork 27
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
Improve tolerance against corrupted data of file system-based storage #21
Comments
Already implemented with better support for skipping invalid storages, and improved logging of corrupted cases. Next is to add note loading errors as well as stability improvements regarding external file changes (reloads) and reloading of the app in between load processes (safe sync operations should be used with backup) |
Notes don't sync for days at a time and restarting the app results in lost information. I've lost critical notes twice this way in the last 2 months. |
Hi, Local boost note does not have sync, can you better explain what happened, do you mean sync to file system? Which version do you have and where have you downloaded it, can you screenshot app UI? |
Current behavior
Boost Note.next app cannot deal with corrupted data in file system-based storage.
Expected behavior
The app should provide some diagnostic tools so users can debug their own note storage
The text was updated successfully, but these errors were encountered: