wjvii

Out of curiosity I tried a database that was not encrypted and got the same exception but I was able to open that database in the SQLite Toolbox in Visual...

@ericsink I had put that in the information above but I didn't format it as code so it didn't show up for some reason after I posted it. I corrected...

Still trying to figure this out so first thing today I grabbed an unencrypted copy of the same database and removed the password from the SqliteConnectionStringBuilder and the same code...

So taking from this https://www.bricelam.net/2016/06/13/sqlite-encryption.html, I wrote a quick .NET Core 3.1 Console app and created a new unencrypted SQLite database with one table and tried to encrypt it by...

@sjlombardo assuming he used the database I sent in the test project above it was created with the latest version of ErikEJ's SQLite/SQL Server Compact Toolbox extension from the latest...

@sjlombardo so is this migration required even though that database has not yet been encrypted at all? TestEncrypted.db was not previously encrypted with any version of SQLCipher.

Not sure if this is required since this database has never been encrypted before but just to be sure I modified the code from @bricelam example above and I added...

@sjlombardo that appears to be the answer here. I was mistakenly under the impression that it encrypted the data once the password was set, at least on an empty database...

@bricelam I can definitely say this was a source of confusion for me as well and I have read many articles on the Internet about SQLite encryption with SQLCipher that...

@sjlombardo I was referring to SQLCipher in particular and I am very glad you directed me to the FAQ and other articles on the Zetetic website as they definitely cleared...