-
Notifications
You must be signed in to change notification settings - Fork 372
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
Lost all notes when updating to newer cloud-based version #1538
Comments
Hi, Can you tell me the reason why you cannot log into slack? Try here: https://join.slack.com/t/boostnote-group/shared_invite/zt-cun7pas3-WwkaezxHBB1lCbUHrwQLXw Just use regular slack login and you should be able to enter. For this issue, if you did have PouchDB (old cloud storages), you can follow this procedure from slack:
If not, you probably had local storage, can you try looking for For PouchDB storage, you need 0.19.x to inspect them, but you also need to load them by the above procedure. |
Current behavior
Latest Boost Note (no version posted anywhere so I will just say as of 11:20PM 3/12/2022) shows sign up/sign in screen I don't remember from previous versions I was running. I cannot be sure but I think I was running a 0.14. The installer I still have around is 0.12.4 but it had been updated in-place since then. Get real confused. Create account on GitHub. Log in. Not seeing any of my old stuff. Rerun the 0.23.1 version. See entries for all of my storage but all of the notes are gone. Everything is just gone.
I found #645 and tried to look in the developer console. I see pouches in IndexedDB corresponding to the different databases I have but non of them have any documents except one that has a stub untitled one I created when trying to figure out if it correlated to my current situation.
Expected behavior
I figured I'd at least see my notes in the old version...
Steps to reproduce
Environment
Desktop/Web
Desktop. Windows 10.
Boost Note 12.4 and I guess Boost Note.next 1.57.1
PS: #645 referenced a Slack but I can't seem to log into it. At any rate, my inference was that the document stores in the pouches were all wiped anyways so it was moot.
The text was updated successfully, but these errors were encountered: