"SQLiteException: not an error": Possible breakage in 2.0.5?

[ericsink]

I'm having this error when upgrading from 2.0.4 to 2.0.5-pre20201231105030, on Android, with sqlcipher.

  SQLite.SQLiteException: not an error
  at SQLite.SQLiteCommand.ExecuteNonQuery () [0x000cd] in <a9edccd8a27f41fdaae16acd8ec0ca8e>:0 
  at SQLite.SQLiteConnection.Execute (System.String query, System.Object[] args) [0x00039] in <a9edccd8a27f41fdaae16acd8ec0ca8e>:0 
  at SQLite.SQLiteConnection.SetKey (System.String key) [0x00026] in <a9edccd8a27f41fdaae16acd8ec0ca8e>:0 
  at SQLite.SQLiteConnection..ctor (SQLite.SQLiteConnectionString connectionString) [0x00126] in <a9edccd8a27f41fdaae16acd8ec0ca8e>:0 
  at SQLite.SQLiteConnectionWithLock..ctor (SQLite.SQLiteConnectionString connectionString) [0x0000b] in <a9edccd8a27f41fdaae16acd8ec0ca8e>:0 
  at SQLite.SQLiteConnectionPool+Entry..ctor (SQLite.SQLiteConnectionString connectionString) [0x0001f] in <a9edccd8a27f41fdaae16acd8ec0ca8e>:0 
  at SQLite.SQLiteConnectionPool.GetConnectionAndTransactionLock (SQLite.SQLiteConnectionString connectionString, System.Object& transactionLock) [0x00028] in <a9edccd8a27f41fdaae16acd8ec0ca8e>:0 
  at SQLite.SQLiteConnectionPool.GetConnection (SQLite.SQLiteConnectionString connectionString) [0x00000] in <a9edccd8a27f41fdaae16acd8ec0ca8e>:0 
  at SQLite.SQLiteAsyncConnection.GetConnection () [0x00005] in <a9edccd8a27f41fdaae16acd8ec0ca8e>:0 
  at SQLite.SQLiteAsyncConnection+<>c__DisplayClass33_0`1[T].<WriteAsync>b__0 () [0x00000] in <a9edccd8a27f41fdaae16acd8ec0ca8e>:0 
  at System.Threading.Tasks.Task`1[TResult].InnerInvoke () [0x0000f] in /Users/builder/jenkins/workspace/archive-mono/2020-02/android/release/external/corert/src/System.Private.CoreLib/src/System/Threading/Tasks/Future.cs:534 
  at System.Threading.Tasks.Task.Execute () [0x00000] in /Users/builder/jenkins/workspace/archive-mono/2020-02/android/release/external/corert/src/System.Private.CoreLib/src/System/Threading/Tasks/Task.cs:2319 

Any idea what's happening ?

Originally posted by @tranb3r in #392 (comment)

[ericsink]

I don't (yet) know what is causing this, but it concerns me.

[ericsink]

Wow. @sjlombardo -- thanks for clearing up the mystery here.