Breaking changes on play store

[Krakoer]

I'm developing an app that's currently on play store closed testing. In a new release, I introduced massive changes in the database structure. Since I'm only on closed testing, I'm okay with my testers loosing all their data, so instead of writing a huge migration, I deleted all steps/schemas, set the database version back to 1 and ran make_migrations to generate my new initial clean state.
When running the app in debug mode, everything is fine. Manually installing the production app bundle after uninstalling the old production app works as well.
However, when I install the app through the store, even after manually deleting the app storage through Android's Storage and cache Clear storage button, I'm getting the error You've bumped the schema version for your drift database but didn't provide a strategy for schema updates...

Why does the app behaves fine when installing the app through ADB but not through the store? How to fix this weird state?

Thanks for your answer!

[simolus3]

Why does the app behaves fine when installing the app through ADB but not through the store? How to fix this weird state?

I don't have an obvious explanation for this either unfortunately. It's worth noting that you'd also get that exception if the schema version is downgraded (e.g. the closed testing version is on say version 3 and now you downgrade to 1 - onUpgrade would be called in that case too). But I'm not sure how that didn't trigger in "Manually installing the production app bundle after uninstalling the old production app works as well".

This was just a regular adb install? Sometimes flutter run auto-uninstalls a previous version if there's a conflict I believe.

[Krakoer]

I used adb install and bundletool, none of these solutions triggered the error.
I just found a solution by running adb shell pm clear <package_name>, although quite inconvenient to run for all testers, it worked. I will avoid making such breaking changes in the future!