You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The pre-populated database file is ignored if the database file with the same name already exists in your database file location.
What is the suggested steps of forcing an app to to get the latest version of a pre-populated database (I have both updated existing rows, and added new ones, but the changes are not reflected unless the app is uninstalled first)?
Rename database to a new unique name
Close connection to old database
Delete old database
Open new database
And repeat these steps (for all versions) every time I make changes?
Is there a guide covering this use case somewhere?
The text was updated successfully, but these errors were encountered:
My apologies for the delay. Assuming the app did not store any user data in the database:
The new version of your app should use a new database with a new name. It should also be smart enough to delete the old database if it exists (or just call sqlitePlugin.deleteDatabase and ignore the success/error callbacks).
Please keep in mind that it is extreemely difficult if not impossible to know how long it will take for users to upgrade their apps. So newer versions of the app should just include the logic to cleanup the old database if it exists.
What is the suggested steps of forcing an app to to get the latest version of a pre-populated database (I have both updated existing rows, and added new ones, but the changes are not reflected unless the app is uninstalled first)?
And repeat these steps (for all versions) every time I make changes?
Is there a guide covering this use case somewhere?
The text was updated successfully, but these errors were encountered: