Incorrect unread emails counters rendered in the Proton UI

[RobertKirchner9]

This is a not-very-serious-but-still-annoying bug. I'm running ElectronMail 5.0.1 on Linux Mint Mate 20.3. As you can see in the attached screenshot, there is a 2 to the right of "All mail" in the folder menu on the left, ostensibly indicating 2 unread messages. But this is spurious. There are no unread messages in any of my folders. Even when I click the "unread" filter in "All mail" itself, nothing shows up. These spurious unread message numbers show up next to various folders regularly. I can't clear them, even by logging out and in again. And the ElectronMail tray icon shows spurious unread message numbers as well.

[vladimiry]

ostensibly indicating 2 unread messages

This unread indication is not part of the ElectronMail project, but https://github.com/ProtonMail/WebClients, so it's irrelevant here.

[prestr]

@vladimiry This is a bug with the app. On both Windows and macOS, I recently signed out of my account and back in (to get Proton Drive access) and ever since doing that I have this issue.

Steps to reproduce:

1. If you're logged into ElectronMail already log out and sign back in with the proton.me entry point, then quit the app.
2. Have 1 unread message in your inbox then launch ElectronMail v5.0.1
3. View the message and notice the Inbox no longer shows a (1) unread message but if you look at All Mail there is still a (1) unread message indicated

If you open All Mail, there's nothing unread. Same thing happens with Labels, if the message in the inbox had a label the label still shows a (1).

Restarting ElectronMail clears it up until you get another new message.

[prestr]

To add to this. If you mark a message as Unread the Inbox shows (1) unread but the macOS dock icon doesn't update nor does the Tray icon on Windows.

[vladimiry]

Do you have the "local store" option enabled in the app for the mail account?

Restarting ElectronMail clears it up until you get another new message.

You could also click "Unload" menu item opened by right mouse click on the account handle button. This action triggers the page reload, and so the proton-web-client gets reloaded too.

I recently signed out of my account and back in (to get Proton Drive access) and ever since doing that I have this issue.

To make the Drive service work, the app forces the "account" auth scope when a new session gets open (so you had to re-sign in into the account), as discussed in #522 (comment). This could potentially introduce side effects as Proton might differentiate some logic based on the auto scope type. There were no other recent major changes in the app, so it's either this auth scope related issue or the Proton's web client change. It's yet to be investigated.

[prestr]

Local store is disabled.

Clicking Unload does refresh, All Mail updates and my Dock icon unread also updates correctly.

[prestr]

If its of any help...

I went back to v5.0.0 and the issue persists, then tried v4.14.0 and it's working fine. So it seems like the issue started happening with v5.0.0.

[vladimiry]

Can confirm that if the "local store" disabled, making the 1 unread email read doesn't wipe the "1" tray indicator nor the "all mail (1)" counter. I normally go with a "local store" option enabled, so didn't notice the issue before. If the "local store" enabled, the tray icon is fine (at least if you make the mails read via the "local store" means) as in this mode tray icon under status update has its own logic, but the "all mail (1)" in the proton's app is still there. Beside if I remove the mail, select the "all mail" folder in the proton-web-client, the summary mails count value displayed at the right page side doesn't get updated with -1 value (so remains static). Everything is fine in the "local store" mode as it handles the mails independently ("all mails" counter is fine, same as the tray update, etc).

I went back to v5.0.0 and the issue persists, then tried v4.14.0 and it's working fine. So it seems like the issue started happening with v5.0.0.

Same user session was used or you signed-in (you can see the open session list in the account's settings app, then go "security" section ...)?

[vladimiry]

There were no other recent major changes in the app, so it's either this auth scope related issue or the Proton's web client change.

I went back to v5.0.0 and the issue persists, then tried v4.14.0 and it's working fine. So it seems like the issue started happening with v5.0.0.

So if the issue was still there in 5.0.0 then it's not related to the "account" auth scope forcing and the remaining issue cause then is the proton web client change itself. If so, then it's likely related to some caching (I've noticed they started using Redux for some needs not so long time ago).

[prestr]

Same user session was used or you signed-in (you can see the open session list in the account's settings app, then go "security" section ...)?

Between switching versions I removed my Proton account from the app then added it back.

[vladimiry]

Between switching versions I removed my Proton account from the app then added it back.

Ok, so "account" auth scope forcing is still an option.