fix(db): drop sqlite3_flutter_libs to stop SQLCipher symbol-clash segfault
drift_flutter pulled sqlite3_flutter_libs, whose bundled plain SQLite exports the same sqlite3_* symbols as sqlcipher_flutter_libs. With both loaded the app segfaulted at startup on Linux desktop when opening the encrypted DB (the app built and the Dart VM started, then crashed natively — "Lost connection"). drift_flutter was unused (we open the DB via our own encrypted executor), so removing it drops sqlite3_flutter_libs and leaves SQLCipher as the only native sqlite provider. 37 tests green; Linux build runs without crashing.
This commit is contained in:
parent
5c607c0f65
commit
c4b80ab4a9
4 changed files with 3 additions and 23 deletions
|
|
@ -24,9 +24,10 @@ dependencies:
|
|||
# Stream combinators (StreamGroup) for reactive multi-table reads.
|
||||
async: ^2.11.0
|
||||
|
||||
# Encrypted local database.
|
||||
# Encrypted local database. NOTE: do NOT add sqlite3_flutter_libs / drift_flutter
|
||||
# — their bundled plain SQLite collides (same symbols) with SQLCipher and
|
||||
# segfaults on desktop. SQLCipher is the only native sqlite provider here.
|
||||
drift: ^2.28.0
|
||||
drift_flutter: ^0.2.4
|
||||
sqlite3: ^2.7.5
|
||||
sqlcipher_flutter_libs: ^0.6.5
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue