Feedback v244.240828.0 - Error - UNKNOWN - linux
Client: linux
Type: UNKNOWN
Tutanota version: 244.240828.0
Timestamp (UTC): Wed, 28 Aug 2024 13:08:14 GMT
User agent:
Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) tutanota-desktop-debug/244.240828.0 Chrome/126.0.6478.185 Electron/31.3.1 Safari/537.36
Error
Error message: AssertNotNull failed : null
Stacktrace:
Error: AssertNotNull failed : null
at assertNotNull (asset://app/app.js:2041:11)
at LoginController.getUserController (asset://app/app.js:152163:16)
at ContactModel.entityEventsReceived (asset://app/app.js:171454:38)
at asset://app/app.js:146757:19
Output in the console:
LoginIncompleteError: Trying to do a network request with encrypted entity but is not fully logged in yet, type: UserSettingsGroupRoot
at EntityRestClient._validateAndPrepareRestRequest (asset://app/worker.js:126417:17)
at async EntityRestClient.load (asset://app/worker.js:126153:59)
at async DefaultEntityRestCache.load (asset://app/worker.js:125653:26)
Describe the bug
Cannot login with paid offline account after migration to tutanota model version 75.
To Reproduce
Steps to reproduce the behavior:
Login with an older desktop client using a paid account.
Update the desktop client to the latest version.
Log in again with the stored credentials.
See error
Expected behavior
The login should work.
Potential fixes
The UserSettingsGroupRoot are deleted in the migration and make the async offline login fail, because we do not wait for the login to complete before trying to load the instance.
We could just delete the User from the offline db and thus prevent the async login from being executed at all.
Output in the console:
Describe the bug Cannot login with paid offline account after migration to tutanota model version 75.
To Reproduce Steps to reproduce the behavior:
Expected behavior The login should work.
Potential fixes
The UserSettingsGroupRoot are deleted in the migration and make the async offline login fail, because we do not wait for the login to complete before trying to load the instance.
We could just delete the User from the offline db and thus prevent the async login from being executed at all.