-
-
Notifications
You must be signed in to change notification settings - Fork 285
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fatal DB Error, duplicate column name #5789
Comments
@M123-dev is in internal, so prob one of the 10-20 ish people impacted by the hotfixes |
Makes sense, but I prefer to double-check. We don't want this bug to happen for thousands of users, do we? |
@M123-dev Then I guess we'd rather be careful. |
Heyy @monsieurtanuki sorry for my admittedly very late response, am on really busy schedule rn. My app on latest internal (seems to be from 19.11. android settings say 4.16.9) I still have the same problem. I haven't seen someone else complain in Slack or somewhere so I guess it's a one time thing with some bad internal version mixing, maybe skipping some migrations. I'm not using the internal version that often. Is it fine to re-install? |
Hi @M123-dev! Unless there's a typo in https://github.com/openfoodfacts/smooth-app/blob/develop/packages/smooth_app/lib/database/dao_osm_location.dart#L67-L90, or for some reason the latest version of
Normally it's fine to reinstall from scratch and it's fine to upgrade, regardless of which tango you danced with the versions. |
@monsieurtanuki just updated again, still happening. Maybe the "Fatal Error" at the beginning 🤷, but I didn't double-check if it's coming from somewhere else in the error catching logic. For me, it is fine to reinstall. Don't have anything important on the Play Store version, but I don't want to uninstall when this is maybe a problem others could face. |
@M123-dev Would you please double-check the displayed error message? There may be a typo in the String I catch and check. |
What
Is the screen I am greeted with. Maybe I have missed some migration script but that shouldn't happen.
The text was updated successfully, but these errors were encountered: