-
Notifications
You must be signed in to change notification settings - Fork 11
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
Issues with accessing exported browser file #33
Comments
I upgraded sqlite3 to: SQLite version 3.43.0 2023-08-24 12:36:59. The only difference in results seems to be
But when I switch the single/double quotes, it works fine:
The message count query when directed to signal.db returns:
|
Some more information, the .db file opens just fine with SQLiteStudio (3.4.4) but nothing else seems to be able to get it to work. |
Please show the output of
My mistake. sqlite3 no longer accepts double-quoted strings. |
This command does not seem to work:
I was trying to use the GUI for DB Browser for SQLite, and this is the information I can get from it:
|
Thanks, that's the information I was after. I'm afraid your version of sqlitebrowser is too old. It has SQLite 3.37.2, but the Signal Desktop database uses a feature that was introduced in SQLite 3.38.0. You could try with a nightly build of sqlitebrowser. Maybe it has a newer SQLite version. |
Yep, that was it. Not sure why I didn't catch that bit in the version information. Thanks for the help! |
Hi, just wanted to say thanks for this tool, it's so much simpler than others I've looked at.
I might be missing something really simple here but I'm trying to access the exported db file using DB Browser for SQLite and I am getting this error:
I made sure Signal was not running when I exported the DB. I am on MacBook Pro, Apple M1 Pro, Ventura 13.4. Here are the outputs for what you mentioned in #26:
Everything you mentioned seems to come back clean but the SQLite browser still won't open it for some reason. Would you happen to have any ideas?
The text was updated successfully, but these errors were encountered: