I had about enough of this extension. Some years ago they changed the storage location of the saved sessions file from someplace (Local Storage\ ?) to Databases\ without warning, meaning my automatic backups were suposedly backing up for months something that didn't actually exist anymore on that location.
And now, after the extension updated itself to v4, *surprise*, not only didn't migrate the SQL session data file, you know, the CORE of our data, to the new format, but also deleted the Database\ folder with said file in it (or let chrome delete it), without even a warning. And only know I realised it.
For months that file is lost, and not a peep from you people. Don't tell me you mentioned it in your blog, like if everyone has to follow every blog of every extension one has, you should have tested the damn thing and converted the database file accordingly after the update (in v3 we could export our file in 3 or 4 text formats, so the conversion function *was there*), but if for some reason you couldn't, you should at least warn the users with a popup message directly in the browser, or opening a webpage like you do when Sbuddy is updated, telling us to convert everything to i.e csv to a safe location, instead of a post on a blog, and then just nuke all of our data...
And no, my drive isn't encripted, no the extension console doesn't give me any errors, I assume because since the file is gone months ago, there're no incompatibility errors now...
Speaking of the console, the repair() command gives me this: Promise {<pending>} lol, really?
Well thank you very much "buddy", but I'm going to find a similar extension that actually takes this thing seriously.
Meanwhile I found this tool of yours
https://sessionbuddy.com/v4-migration/ which should be frontpage on the extension itself instead buried under several pages on your blog, and it converted my 5 month old file. Of course it couldn't be smooth, to it demanded actual google chrome and not a chrome based browser, and still only at the 2nd attempt it actually saved a real file instead fo a 0 bytes file, but at least it's something.