Splitting `IndexedDB` table when migrating from `CRA` to `vite`

[imblowfish]

Hello, we encountered the problem when we tried to migrate our ionic v6.0 (CRA) project to ionic v7.0 (vite). Withing this migration we removed CRA specific files and added vite specific files, while not touching the code for working with @ionic/storage, the same drivers are used there (IndexedDB + localStorage), the name is the same.

After the migration, we started testing the update on an Android smartphone and found that changing the version meant that the app no ​​longer saw data from storage. However, if you reinstall the previous version, the data is restored.

This behavior is specific only to mobile devices, on the web under desktop or mobile the error is not reproduced.

I checked IndexedDB via the Android debugger in Chrome and saw that ``IndexedDB` and the data in the Storage section in DevTools are indeed erased, while the amount of memory in the Storage section of the device settings shows that the memory required for the application has not decreased.

It looks to me like after switching from CRA to vite we now have 2 IndexedDBs in the phone's memory, but for some reason CRA can only connect to its own, and vite can only connect to its own in the app itself.

Can you suggest any solutions to this problem?

[imblowfish]

Looks like we found the root cause in the @capacitor/core. We used v5.0.5 on CRA app and after vite migration we upgraded it to v6.2.0 and the error appeared

For now we decided to downgrade our version back to v5 and upgrade only minor version to v5.1.1

I don't think the error is related to storage, but I'll leave the issue open for you to decide.

[imblowfish]

@capacitor/core team helped us with this problem
ionic-team/capacitor#7832