QueryAsync<> does not work for me after switching to sqlite-net-sqlcipher (v1.5.231).

[spazjr01]

I recently discovered that my database needed to be encrypted. I had everything working with sqlite-net-pcl (v1.5.231). Because of the need for an encrypted database. I removed sqlite-net-pcl and replaced with sqlite-net-sqlcipher. Then, I added the following code to key the database for encryption:

public SQLiteAsyncConnection GetConnection()
{
//var personalPath = Environment.GetFolderPath(Environment.SpecialFolder.Personal);
var personalPath = Android.OS.Environment.ExternalStorageDirectory.AbsolutePath;
var path = Path.Combine(personalPath, "databases\TPS.db");
string password = "SecretPassword";
SQLiteAsyncConnection sqLiteAsyncConnection = new SQLiteAsyncConnection(path, storeDateTimeAsTicks: true, key: password);
sqLiteAsyncConnection.QueryAsync("PRAGMA key='?'", password);
return sqLiteAsyncConnection;
}

I pulled the db across and it appears to be encrypted. I was able to open the db in DB Browser for SQLite using the encryption password. So far so good.

However, my commands to the database using QueryAsync<> no longer retrieve records. There is no error that I can see in debugger or device monitor tool. There are just no records retrieved. However, using the Table<> command, I am able to retrieve the records. Is QueryAsync<> broken in sqlite-net-sqlcipher, or am I doing something wrong? See code sample below:

This works:
var manifests = await App.TPS_Database.DBConnection.Table<Manifest_T>().OrderBy(m => m.Name).ToListAsync();

But, this does not work, but it used to. For complicated queries, I needed this to work:
var manifests =
await App.TPS_Database.DBConnection.QueryAsync<Manifest_T>("select ID, Name from Manifest_T");

[lnaie]

I don't have an encrypted db, but all my queries, that used to work otherwise, now fail with the latest version. any idea where the problem might be?

[praeclarum]

Hello, the SQLCipher library has been updated. Would you mind testing against 1.6-beta and letting me know if this is still a problem?

[spazjr01]

I apologize for the delayed response. But, I tried to test this and found the following:

When I updated from 1.5.231 to 1.6.258-beta, the following occurs:
The statement that I used to key the database stopped working. This means the first statement in the following no longer works, because there is no longer an constructor overload for this. Error: The best overload for 'SQLiteAsyncConnection' does not have a parameter named 'key'

SQLiteAsyncConnection sqLiteAsyncConnection = new SQLiteAsyncConnection(path, storeDateTimeAsTicks: true, key: password);
sqLiteAsyncConnection.QueryAsync("PRAGMA key='?'", password);

Once I removed the invalid parameter from the instantiation and retested,... yes, the QueryAsync function now works. But, my database is no longer encrypted. I tried to use the code on the site to set this up as below, but that the below code for SQLiteConnectionString also no longer accepts the additional key parameter. What gives?

var options = new SQLiteConnectionString(databasePath, true,
key: "password");
var encryptedDb = new SQLiteAsyncConnection(options);

[vilavlooi]

I had the same error however in my case I had called the parameter with an upper case 'K' (Key) instead of lower case 'k' (key) your code shows lower case already I know but maybe someone in the ether also used an upper case 'K'