I’ve been trying to get answers from Proton for literal months concerning critical functionality issues with their mobile Android client. Messages are often truncated / missing data; clearly, there’s a disconnect between the cached version of the message and the message the user sees. Unfortunately, every attempt to resolve this with support is met with boilerplate “try our beta app” at best, ghosting at worst.
I have supported Proton as a paid user since 2018. It would be nice to think that they value their early adopters, but… honestly… their actions suggest otherwise.
Edit: Proton acknowledges the issue, offers no timeline for a fix:
Please be informed that the issue has been reported and our developers are aware, they are look for fixing it in one of the future updates of the app. Unfortunately, we cannot provide an ETA on when the permanent fix will be available.
You mean the email? I never had anything resembling the issues you describe.
I mean the email. Apparently it is a known issue for some people on the Android client. I tend not to use the client to send, but my partner does regularly. Out of every three messages, at least one is missing data at the end of the message. It does not seem to be device specific.
Well that would be frustrating. I haven’t experienced that. But two things that may ne somewhat related.
If I preview a mail and reply, then if the original message did not finish downloading content then it seems temprarily unavailable in my reply. Which I have had same issue in MS Outlook, fairmail etc.
Occasionally hitting reply takes sometime for email chain text to load. initally it appeara missing but show up as I type.
And obviously if I don’t hit load remote content that content is not available.
It is possible it is device related?
Did you try Beta App that may have fixes?
We did try the beta app, a few times. Generally we notice it on the other end; the recipient (especially one external to Proton) gets a truncatesd message or rarely, an empty one. I am 90% certain it has to do with the way Proton saves drafts before sending; I’d bet that it is not verifying the displayed version (user’s version) against the last draft.
Very strange. I’ve used Proton roughly as long as you have, and have never had any of these issues with the Android client. I send emails from my phone all the time, even important ones.
Regardless, Proton acknowledges the issue:
Not exactly a stellar reply, given that their business revolves around their email offering.
That sounds like a good deduction