Simon Choi

@robotoss Thanks a lot! This looks to me like the previous process is still blocking the database file so the new Isar instance cannot access it. Let me do some...

@robotoss do you only observe this behavior only after killing and restarting the app (with the back button) or also while the app is running?

Okay then the most likely explanation is that Android does not immediately release the file lock or the mmaped memory. I'm not sure if/how we can fix that. I wonder...

That's super helpful thanks @Chappie74. My issue right now is that M1 macs cannot run x86 emulators 😞

This is fixed in version 3.0.1

This is a known issue and will be fixed for stable Isar v3.

Going to close this since the old inspector won't receive any updates

Something seems to prevent Isar from loading the web library. Do you see a request for Isar web javascript?

Closing in favour of #686

Which `isar_flutter_libs` version are you using?