Simon Binder

I can't think of any scenario where the Flutter engine would terminate the main isolate but keep a background isolate running... If that happened there wouldn't be any way to...

Thanks for the report. Nothing stands out from the code (it looks very similar to some examples in this repository that work). Could you check which drift version you're using?...

Any information on the method you're calling first? Can I copy your code and just call any method to reproduce it? And just out of interest, does the error go...

I'm afraid I need more information to act on this. - After you added the `feature_selection_v2` table to your database (on `@UseMoor`), did you write a schema migration for it?...

This might be related to https://github.com/simolus3/moor/issues/135. Can you make sure that you're using `moor: 1.7.2` (maybe use `flutter_upgrade`).

Thanks for the info. Do you know how often that happens (if you delete your app's data and reinstall the app, does that error occur every time?). Can you try...

Thanks for the detailed insights! I now have a better idea of what's going on. > please do check the screenshot below. Do you think this might cause any problem?...

> but i open database only one time Interesting. But is feature_section_v2 the only table where this happens? If it only happens on databases that are not a singleton, then...

One more thing that comes to my mind: Did you re-use a filename somewhere? E.g. is the database with the feature selection table passing the same path to the `FlutterQueryExecutor`...

Uh oh. Can you try enabling the `logStatements` option on the `FlutterQueryExecutor`? Does the `CREATE TABLE` statement for the missing table appear at all? ~~Another shot might be to look...