Protonmail: All emails disappear from inbox (and reappear, then disappear again...)

Here is an update.
I tried clearing the cache, thanks @danhead for the tip :slight_smile:
It didn’t fix the issue but allowed me to observe more carefully what happens during the sync.

Basically, clearing the cache of ProtonMail Bridge removes all email data and disconnects my account. So on MailSpring’s side it’s kind of like a sync reset of some sorts I guess. Anyway here’s what happens:
m

When MailSpring first scans the folders, the Inbox is “coherent” (all the messages that should be there are there).
During “scanning/browsing” of the other folders (“balayage” in French, when the green circle is slowly blinking next to all the folders), it’s fine.
The issue happens at the same time than this scanning is over. All email disappear progressively from the Inbox in a few seconds after the end of the scanning.
Hope this helps :wink:

Another element of interest: whenever I start the app, the Inbox is coherent. The inbox empties itself after a time (a few minutes usually). I haven’t seen any event that seems to trigger the emptying.

1 Like

Same issues here, does anyone have any new info on this? I watch all my emails disappear and then there’s a message that says “Hooray! You’re done.”

1 Like

I don’t know when exactly this’ll be something that Ben can look at. There are a lot of things to do! However, because Mailsync is now open source, anyone else tech-savvy is encouraged to take a look. (Yes, I know the Mailsync build system doesn’t work outside of Ubuntu 16.04 right now…that’s what I’m working on.)

If there is anything I can do to progress this issue to its resolution, let me know. I can follow troubleshooting steps, send log files, etc. For me, it does appear the emails are being archived in Mailspring, but are still in the inbox in ProtonMail itself. They disappear (Hooray! You’re done), then re-appear, disappear, etc.

1 Like

Heads up, @bl00mber is trying to debug this one in hopes of possibly addressing it in a related PR:

1 Like

Potential fix for this bug in:

Thanks, @bl00mber!

(PR now awaiting review/testing)

1 Like

How can we get this review taken care of?

1 Like

Is something else missing to merge this changes? if it needs more testing im willing to help

Is this supposed to be fixed by the (now merged) PR? I’m still getting the same issue.

1 Like

Now March 12, 2022 and issue remains for protonbridge users.

Please, guys, try to fix this. This disappear and reappear issue really annoys me. Thanks!

I would also appreciate if this issue could be fixed. It’s honestly the only thing preventing me from purchasing the pro version of the software and using it as my main email client.

Hi everyone,
have the same bug.

It’s really frustrating, because Mailspring, while re-syncing all the mails, uses A LOT of web traffic.
My Mailbox is about 2GB, and the Mailspring/ProtonBridge has over 35GB of Download Traffic in the last few days…

same issue here! A fix would be highly appreciated

I solved this by disabling local cache on the Proton Mail Bridge app.

Restart of the bridge is required.

I tried your procedure @maximgx. Unfortunately that did not solve the problem for me.

Yes, for some reason, it only worked for me for a while, then the problem returned @aseedb .

Now however, when I hit F5 a couple of time all the emails appear. But when I restart the app have to hit again F5 until it shows.

@maximgx Yes in my case it also keeps reappearing after a while. But I can see that protonmail bridge is generating a huge network traffic. I think it keeps downloading the mailbox again and again.

I have the same issue with protonmail, disabling the cache on proton bridge didn’t help. I have to keep hitting F5 to see my email and the most annoying part is when you are trying to write a reply and it keeps disappearing.
Is this really not solved by now since 2017?

I cannot use Mailspring until this ProtonMail issue is reliably resolved - which is a great pity, since it seems excellent.

I am also bringing the issue up with ProtonMail.

Replying here to see updates on this issue, please!