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
I didn't want to make it too long - and didn't want to have to edit it more if not necessary 😉... I hope you get the problem already with the current video - but I describe how it went on after the end of the video (and if you want the rest of the video, please say so, then I will edit the rest):
as I was logged in: still the same error message
as I set up "lock with biometrics": still the same error message (at first)
then I quit the app completely
after that - first opening of the app with biometric-unlock: that error message is gone...
I hope that already helps!
I use Argon2 since last year. If you want to know the specific settings, I would have to look it up. (but I can already say I don't use the default settings, but "hardened" it a bit)
PS: Before making the video, I logged out. But: I didn't delete any cache... As you can see in the video, the error message pops up already by opening the app (even before entering my master password) - so I don't know if KDF can interfere with that... But: I can not say if this was the same directly after installation of the beta and firtst start (and when there was no login or user data there)?!
Steps To Reproduce
After (first) login - in my case via master password and FIDO2 WebAuthn - I get that error message every few seconds:
When I click "wait", the message comes up again after a few seconds. And this seems to go on endlessly.
Then I set up a few things, including unlocking via biometrics (fingerprint). After that change of settings, the error message was gone.
Expected Result
No error messages.
Actual Result
Error messages.
Screenshots or Videos
See above.
Additional Context
Cloud (EU-server region)
Operating System
Android
Operating System Version
Android 13
Device
Fairphone 5
Build Version
2024.6.1 (11139)
Beta
The text was updated successfully, but these errors were encountered: