Skip to content
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

Database error after update to version v252.241122.0 #8044

Closed
2 tasks done
jackwilliams79 opened this issue Nov 27, 2024 · 5 comments
Closed
2 tasks done

Database error after update to version v252.241122.0 #8044

jackwilliams79 opened this issue Nov 27, 2024 · 5 comments
Labels
bug broken functionality, usability problems, unexpected errors

Comments

@jackwilliams79
Copy link

  • This is not a feature request (existing functionality does not work, not missing functionality).
    I will request features on forum or via support.
  • I've searched and did not find a similar issue.

Bug in mobile app

Describe the bug
After updating to version v252.241122.0 on Android, the following error message is shown everytime the app is opened:

Feedback v252.241122.0 - ProgrammingError - UNKNOWN - androidClient: android Type: UNKNOWN Tutanota version: 252.241122.0 Timestamp (UTC): Wed, 27 Nov 2024 16:31:08 GMT User agent: Mozilla/5.0 (Linux; Android 15; Pixel 8 Build/AP3A.241105.007; wv) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Chrome/131.0.6778.81 Mobile Safari/537.36 ProgrammingError Error message: You forgot to migrate your databases! sys.version should be >= 114 but in db it is 112 Stacktrace: ProgrammingError: You forgot to migrate your databases! sys.version should be >= 114 but in db it is 112 at Hc.checkStateAfterMigrations (https://assets.tutanota.com/mail-worker.js:23:63094) at async Hc.migrate (https://assets.tutanota.com/mail-worker.js:23:62872) at async Ws.init (https://assets.tutanota.com/mail-worker.js:1:19717) at async pc.getStorage (https://assets.tutanota.com/mail-worker.js:23:50139) at async pc.initialize (https://assets.tutanota.com/mail-worker.js:23:49906) at async qo.initCache (https://assets.tutanota.com/mail-worker.js:23:10521) at async qo.resumeSession (https://assets.tutanota.com/mail-worker.js:23:7331)

To Reproduce
Steps to reproduce the behavior:

  1. Not sure how to reproduce an app update on Android
  2. Just start the app
  3. Error message occurs

Expected behavior
Normal functioning app. No error message

Screenshots

Smartphone (please complete the following information):

  • Device: Google Pixel 8
  • OS: Android
  • Version: 15

Additional context

@jackwilliams79 jackwilliams79 added the bug broken functionality, usability problems, unexpected errors label Nov 27, 2024
@dillymyers
Copy link

Got the same problem after updating my app through F-Droid just now, can't see any other problems though

@Gitchick57
Copy link

Gitchick57 commented Nov 28, 2024 via email

@Piscium
Copy link

Piscium commented Nov 28, 2024

Just updated from F-Droid, got the same error message as the OP.
I also get the message every time I start the app. I had no issue before this update. I am also on Pixel 8, Android 15 (GrapheneOS).
Despite the error message things seem more or less normal, I have not done a full test to see if anything is broken.
The error message looks scary though, especially if the bit about the databases is at the server rather than the Android client, as then I could lose messages.

@charlag
Copy link
Contributor

charlag commented Nov 28, 2024

Hi, sorry about the issue, F-Droid tag was pointing to the version without the fix which is our oversight.

Upgrading to the next release (253.241126.2) or simply deleting your credentials and logging in again should automatically fix it.

I will close the issue now as it should be fixed by upgrading to the next app version.

@charlag charlag closed this as completed Nov 28, 2024
@jackwilliams79
Copy link
Author

@charlag Thanks for the info. Good to know that a fix is already implemented. In F-Droid the newer version is currently not yet available. In the meantime, logging out of the app and logging back in does really solve the problem.

@charlag charlag pinned this issue Nov 28, 2024
@hrb-hub hrb-hub unpinned this issue Dec 9, 2024
@hrb-hub hrb-hub pinned this issue Dec 9, 2024
@BijinDev BijinDev unpinned this issue Jan 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug broken functionality, usability problems, unexpected errors
Projects
None yet
Development

No branches or pull requests

5 participants