[SQLiteStore] Accept SQLITE_MISUSE for sqlite3_config(SQLITE_CONFIG_URI, 1)

[DmitriyKirakosyan]

This PR fixes a crash when using the library along with another library which consumes SQLitePCL.raw.
The library should not throw exception if raw.sqlite3_config(raw.SQLITE_CONFIG_URI, 1) returns SQLITE_MISUSE as it would mean that the config was already set.
See microsoft/appcenter-sdk-dotnet#1725 (comment) for details.

https://github.com/Azure/azure-mobile-apps/issues/573
microsoft/appcenter-sdk-dotnet#1725

---

NOTE: I haven't tested the changes.

[adrianhall]

Thanks for this. It passes all tests, but I'll take a look at this PR on Friday.

[amertlich]

This fixes the exception thrown after SqlitePCL.raw.sqlite3_config but I still get an exception thrown after the subsequent open call here: https://github.com/Azure/azure-mobile-apps/blob/main/sdk/dotnet/src/Microsoft.Datasync.Client.SQLiteStore/Driver/SqliteConnection.cs#L59

I still have to use the workaround described here even with 5.0.21
microsoft/appcenter-sdk-dotnet#1725 (comment)

[adrianhall]

Please open a new issue with the actual error you are receiving. We accept SQLITE_MISUSE now, so it's something else going wrong. Without an appropriate error, we can't fix it.

[amertlich]

I'll have to clone and reference the source repo since the return code is not bubbled up and I just get the general exception. I'll try to get to it soon.

[amertlich]

So I've been dealing with this workaround and decided to remove it and found it's still not working.

The error code it's responding with is (14) SQLITE_CANTOPEN

  at Microsoft.Datasync.Client.SQLiteStore.Driver.SqliteConnection..ctor (System.String connectionString)
  at Microsoft.Datasync.Client.SQLiteStore.OfflineSQLiteStore..ctor (System.String connectionString)
  at Microsoft.Datasync.Client.SQLiteStore.OfflineSQLiteStore..ctor (System.String connectionString, Microsoft.Extensions.Logging.ILogger logger)

Should I open a new bug for this?

I'm leaving the workaround in place for now -- which is to just let the mobile apps SDK initialize SQLite first, before app center does.

[kj4bix]

Using 6.0.4 I still get the (14) exception if I already have another SQLite instance/connection open.

If I only use the datasync.client (SQLite) there is no issue. Opening a SQLite database before letting datasync.client open it's database gets the 14 exception above. Even though it works fine without the other database. 6.0.4 has the check for MISUSE which allows it to get further.