Use version 3.x of sqlite3 package

[RoarGronmo]

When trying to migrate one our projects to sqlite3 3.0.0 (since flutter pub get showed a new 3.0.0 version of sqlite3), following the description on how to migrate here we met this problem:

C:\FlutterProjects\mOffice git:[78-rework-layout-of-mmap2_b1]
flutter pub get
Resolving dependencies... (7.2s)
Because drift_dev >=2.23.0 depends on sqlite3 ^2.4.6 and m_office depends on sqlite3 ^3.0.0, drift_dev >=2.23.0 is forbidden.
So, because m_office depends on drift_dev ^2.28.0, version solving failed.


You can try the following suggestion to make the pubspec resolve:
* Consider downgrading your constraint on sqlite3: flutter pub add sqlite3:^2.9.4
Failed to update packages.

drift_dev version was set to 2.28.0, which I think is fairly new...

Anyway, will there be a migration guide for drift to sqlite3 v3.0.0, or will it be provided "out-of-the-box" in a future drift release ?

[RoarGronmo]

Was trying the latest sqlite3.wasm (in hope it would work for <3.0.0 of sqlite3), and got this error when launching my app in web chrome:

[ +112 ms] RethrownDartError: LinkError: WebAssembly.instantiate(): Import #18 "dart" "dispatch_xFunc": function import requires a callable
               ===== asynchronous gap ===========================
           dart-sdk/lib/_internal/js_dev_runtime/patch/core_patch.dart 749:28                get current
           package:drift/src/remote/communication.dart 113:66                                request
           package:drift/src/remote/client_impl.dart 175:10                                  <fn>
           dart-sdk/lib/_internal/js_dev_runtime/patch/async_patch.dart 623:19               <fn>
           dart-sdk/lib/_internal/js_dev_runtime/patch/async_patch.dart 648:23               <fn>
           dart-sdk/lib/_internal/js_dev_runtime/patch/async_patch.dart 542:3                _asyncStartSync
           package:drift/src/remote/client_impl.dart 165:16                                  ensureOpen
           package:drift/src/utils/lazy_database.dart 74:49                                  <fn>
           dart-sdk/lib/async/zone.dart 1849:54                                              runUnary
           dart-sdk/lib/async/future_impl.dart 222:18                                        handleValue
           dart-sdk/lib/async/future_impl.dart 948:44                                        handleValueCallback
           dart-sdk/lib/async/future_impl.dart 977:13                                        _propagateToListeners
           dart-sdk/lib/async/future_impl.dart 720:5                                         [_completeWithValue]
           dart-sdk/lib/async/future_impl.dart 804:7                                         <fn>
           dart-sdk/lib/async/schedule_microtask.dart 40:34                                  _microtaskLoop
           dart-sdk/lib/async/schedule_microtask.dart 49:5                                   _startMicrotaskLoop
           dart-sdk/lib/_internal/js_dev_runtime/private/ddc_runtime/operations.dart 118:77  tear
           dart-sdk/lib/_internal/js_dev_runtime/patch/async_patch.dart 188:69               <fn>


           dart-sdk/lib/_internal/js_dev_runtime/private/ddc_runtime/errors.dart 307:10      createErrorWithStack
           dart-sdk/lib/_internal/js_dev_runtime/patch/core_patch.dart 280:28                _throw
           dart-sdk/lib/core/errors.dart 120:5                                               throwWithStackTrace
           dart-sdk/lib/async/zone.dart 1512:11                                              <fn>
           dart-sdk/lib/async/schedule_microtask.dart 40:34                                  _microtaskLoop
           dart-sdk/lib/async/schedule_microtask.dart 49:5                                   _startMicrotaskLoop
           dart-sdk/lib/_internal/js_dev_runtime/private/ddc_runtime/operations.dart 118:77  tear
           dart-sdk/lib/_internal/js_dev_runtime/patch/async_patch.dart 188:69               <fn>

I suspect this version of sqlite3.wasm not to work with sqlite3 < v3.0.0.

[simolus3]

It is true that that version 3.x of package:sqlite3 needs a new sqlite3.wasm, and that file is not compatible with older versions of package:sqlite3.

Of course, drift will update to the latest version of package:sqlite3 soon. That release did change a few things that affect drift and its documentation though, so it will take me a couple of days to get everything ready. I generally expect this migration to take a while, and I will keep supporting version 2.x of package:sqlite3 for a few months to make this easier.

So my suggestion for now is to keep using version 2.x, but thanks for filing this issue! I'll post updates here as they come in.

[deminearchiver]

sqlite3 v3 now uses build hooks. Upgrading to the new version would require dropping the dependency on sqlite3_flutter_libs and sqlcipher_flutter_libs from our projects. Will any other changes need to be made, or will this upgrade be straightforward?

[simolus3]

Dropping these dependencies is mostly what I'll be doing, yes. But the docs also mentions sqlite3_flutter_libs in a bunch of places, and I need to update them / make sure all examples continue to work and all that :)

[simolus3]

Small update on this: There are a few bugs remaining with native assets on Flutter (one preventing macOS releases to the App Store, and a minor one causing issues on Linux if lld has not been installed).

Since drift can't support versions 2.x and 3x of the sqlite3 packages at the same time, I might delay this a bit until those initial issues have been fixed. I also want to point out that I'm still maintaining version 2.x of sqlite3 for a while, so there's no risk of dependency rot at the moment.

[nikolaspateras]

Starting November 1st, 2025, Google Play requires all new apps and updates targeting Android 15+ to support 16 KB page sizes on 64-bit devices.

When updating to latest drift version, it uses version 2.9.4 of sqlite3 and it's not possible to publish an app in play store:

[simolus3]

@nikolaspateras Please don't derail this issue, you can file seperate ones for this. But either way:

• versions 0.5.25 and later support 16KB page sizes, check your version.
• libsqlite3.so for armeabi-v7a is a warning. armv7 is a 32-bit architecture where 16KB sizes aren't supported either way. There is no Play Store requirement to use 16KB-aligned segments for that architecture.

So I think sqlite3_flutter_libs contributed the non-critical warning here, but that's it. Let me know (with an issue on this repository) if you have actual Play Store verification problems.

[nikolaspateras]

@nikolaspateras Please don't derail this issue, you can file seperate ones for this. But either way:

• versions 0.5.25 and later support 16KB page sizes, check your version.
• libsqlite3.so for armeabi-v7a is a warning. armv7 is a 32-bit architecture where 16KB sizes aren't supported either way. There is no Play Store requirement to use 16KB-aligned segments for that architecture.

So I think sqlite3_flutter_libs contributed the non-critical warning here, but that's it. Let me know (with an issue on this repository) if you have actual Play Store verification problems.

Thank you, I wasn't trying to derail the issue, I just thought that because the 3.x version wasn't supported, i was missing the compatibility but yea as you said it's not mandatory which i realized later, even tho the script shows that the 16kb page is failing, play store doesn't prevent me from it.

[RoarGronmo]

@simolus3 just planning parts of my next year, I just wonder approx when do you think drift is sqlite3 v3.x ready (and maybe when will 2.x support be deprecated )?

And do we need to make major changes in our codebases to comply ?

[simolus3]

I think flutter/flutter#178602 is a blocker for native assets, there are potential App Store upload failures when depending on packages with native assets.

For package:sqlite3, I feel comfortable maintaining the two versions for a while, but drift is a much larger project. So I will likely deprecate 2.x shortly after migrating drift, and I will migrate drift once that issue is resolved on a stable Flutter version. Because it depends on Flutter, I can't give an accurate ETA.

The good news is that I don't expect that any "major code changes" should be necessary. If you're not using a custom SQLite build, it should be as simple as just updating. If you're using SQLite with SQLCipher, some minor changes will be required.

[Vonarian]

Hello,
Is there something we can do to build and debug in web without downgrade, or is it necessary?

[simolus3]

At the moment, you'd have to download a 2.x release sqlite3.wasm to use with drift. But again, those releases are still maintained, so I hope that this is not a problem.