[Bug] email doesn't unlock

[vladimiry]

[Bug] email doesn't unlock

[vladimiry]

I've significantly enhanced a logging feature and looks like noticed a pattern. If the guess is correct, then a reliable fix is coming shortly.

Btw, it will be possible to change app log level with next release, defaults to error level:

[vladimiry]

Closing as resolved.

[vladimiry]

Tutanota support got added just about two weeks ago with v1.0.0, while Protonmail is supported from the day one. So there definitely remain things to improve.

One of the reasons for adding logged-in state indication feature was in enabling a clear highlighting that something went wrong with auto-login process. Auto-login feature might get broken for example if the email provider changes its web UI, since app interacts with it resolving elements on the page by ankers hardcoded in the code (CSS selectors). But this issue doesn't seem to be about this case since for you it doesn't work sometimes, not always, which makes it even harder to detect a pattern.

I tweak the mail providers injection code time to time and so hopefully auto-login feature for Tutanota will be improved over time.

[jeroenev]

not sure if it helps but it seems like it's usually only the one that is in focus that fails to login
even if i don't click anywhere/type anything.

[joshirio]

I can confirm this. I have this issue since the app was renamed to email-securely-app. I have 3 protonmail accounts and on the first start after a fresh boot (linux, KDE) one of the logins gets stuck (not using 2FA). After a restart of the app it always works on the second time. Around 10% of the time it works right away on first try,

Maybe the UI is too slow (web loading) and the app tries to login before the form is ready? This is my guess, because on the second start the app loads much faster since it is not a cold boot.

[vladimiry]

I initially thought it's only about Tutanota, but it's not, thanks for giving more details.

[vladimiry]

Maybe the UI is too slow (web loading) and the app tries to login before the form is ready?

App resolves form elements on the page with a timeout (current value is 10 seconds). So there would be a timeout error displayed in case of form elements resolving failing. But it could be that email provider's JS code was not yet fully loaded/initialized, event though form was already displayed.

[joshirio]

I noticed that it is possible to reproduce this while downloading something (maxing out the download bandwidth). Looks like it happens more likely on slow internet connections.

[vladimiry]

Auto-login stability has been improved with v1.3.0 pre-release. Let's keep issue opened for a while. Then in case of no new reports will turn release to stable and close.

[jeroenev]

looks good
did some basic testing (quitting the app, restarting the app, starting the app after rebooting...) and it seems to be reliable now, restarted the app about 15 times and the issue hasn't occurred once
👍 from me

[vladimiry]

Great, so fix is reliable. Keeping issue opened for a few days awaiting more possible feedbacks.