Not able to auto login

[doraeric]

Not able to auto login

[vladimiry]

@lxgr-linux thanks for the update.

Based on this issue, and other cases too, I could say that "app <=> @electron webview" interaction, on some systems and for so far unclear reason, is a sensitive area of @electron. As pointed before, for the next release, I'm going to disable background throttling for webview's "webContents" guessing that this might increase named interaction stability.

Another option is replacing "app <=> @electron webview" interaction with communication via the main @electron channel, used as a simple events/signals redirection thing. So instead of direct "app <=> @electron webview" interaction, the main process would be in the middle "app <=> main <=> @electron webview". Besides, this approach would likely benefit the "context isolation" enabling need as when I tried it before, the direct "app <=> @electron webview" interaction had some issue in relation to "context isolation". But this would increase the code complexity and would require some refactoring, so this approach is undesirable.

[vladimiry]

The notification channels has to be setup, so the further "app <=> @electron webview" interaction logic works as designed, including secure persisting the active session for reuse it on the next app start. The log error indicates the issue with notification channel establishing, the timeout error.

Why this happens is unclear at the moment, as there is no error cause in the log, so the request for notification channel setup just hangs somewhere in the @electron/@chromium internals. Some other users experience similar issues, see #648 for example.

I guess I could disable the background throttling for webview's "webContents", and we see then if it increases the "app <=> @electron webview" interaction stability.

For now, if you run Linux, consider other package types, like for example flatpak-based one. Writing this because the issue like this might be potentially related to environment specifics (it stopped working for you a few months ago, for some reason, like for example update on your environment), and "flathub" comes with some environment isolation capabilities.

[lxgr-linux]

This is happening to me since the last update.

[doraeric]

I tried flatpak-based version, and it works fine. There is no longer a need for a captcha, and the session remains valid the next time the app starts.
Maybe it's caused by the environment like you said.

[lxgr-linux]

For me this is back working on my arch system.

[vladimiry]

I'm going to disable background throttling for webview's "webContents" guessing that this might increase named interaction stability.

The backgroundThrottling: false flag is already there for at least 3 years,

ElectronMail/src/electron-main/window/constants.ts

Line 18 in c5f76ec

backgroundThrottling: false,