sqflite-testing-and-platforms

Add sqflite_common_ffi as a dev dependency, call sqfliteFfiInit() once, then set databaseFactory = databaseFactoryFfi before any openDatabase call. Use inMemoryDatabasePath for fast isolated tests, since the sqflite plugin itself throws MissingPluginException under flutter test.

Use databaseFactoryFfiNoIsolate instead of databaseFactoryFfi in testWidgets, because the isolate-based factory hangs inside the widget test binding. Call sqfliteFfiInit() first, then open databases normally with openDatabase.

Yes, via alternative factories: sqflite_common_ffi provides databaseFactoryFfi for Windows, Linux, and Dart VM, and sqflite_common_ffi_web provides databaseFactoryFfiWeb for browsers. Assign the factory once in main() before runApp, selecting with kIsWeb and Platform checks.

MissingPluginException occurs because flutter test has no native SQLite and the sqflite plugin only registers on Android, iOS, and macOS. Fix it by pointing databaseFactory at databaseFactoryFfi from sqflite_common_ffi in your test setup.

Wrap the factory with SqfliteDatabaseFactoryLogger from package:sqflite_common/sqflite_logger.dart to capture each statement, arguments, results, and duration. The one-liner databaseFactory.debugQuickLoggerWrapper() also works but is deprecated so it is not left in production.

The 10-second locked warning almost always means a call was made on db inside db.transaction((txn) ...) instead of using the txn object. Use Sqflite.setLockWarningInfo to adjust the watchdog duration and callback.