Skip to content
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

error: pysqlcipher3.dbapi2.DatabaseError: file is not a database #10

Open
ChristopherA opened this issue Oct 1, 2019 · 8 comments · May be fixed by #14
Open

error: pysqlcipher3.dbapi2.DatabaseError: file is not a database #10

ChristopherA opened this issue Oct 1, 2019 · 8 comments · May be fixed by #14

Comments

@ChristopherA
Copy link

I have already done

brew install sqlcipher
pip3 install pysqlcipher3 --user

However, when I cd to the directory with config.json and run python3 ../scab.py I get:

Traceback (most recent call last):
  File "../scab.py", line 41, in <module>
    c.execute("SELECT json, id, name, profileName, type, members FROM conversations")
pysqlcipher3.dbapi2.DatabaseError: file is not a database

Any suggestions?

@ekkis
Copy link

ekkis commented Oct 5, 2019

ugh. I just posted about this. should have checked the history. I have the same issue

@ekkis
Copy link

ekkis commented Oct 5, 2019

the problem is with this compatibility update: #3 -- if you comment out lines 29-33 of the scab.py it should work. it did for me

@tkrunning
Copy link

Thanks @ekkis! That worked for me too, although I had to comment out line 30-33, not 29.

@brummski
Copy link

hi! did not work for me, any suggestions?
thx

@lol-fi
Copy link

lol-fi commented Mar 7, 2020

@brummski did you try commenting out 30-33 as @tkrunning mentioned? 29-33 for me still caused the error, but 30-33 and it ran perfectly

@ryanpcmcquen
Copy link

@mattsta, can we get these permanently commented out?

@lol-fi
Copy link

lol-fi commented Mar 30, 2020

@mattsta, can we get these permanently commented out?

why not make a pull request?

@501st-alpha1
Copy link

I just posted in #13 about why this happens; this is probably a SQLCipher version mismatch, and I presume commenting out those lines causes the library to fall back to the default of version 4, which is now what Signal requires.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

7 participants