Particular encrypted message composes of 3 attachment (noname, encrypted.asc, public_key.asc) doest appear correctly in the browser extension

[martgil]

Description:
The user reported a scenario wherein the appears to be encrypted message in the attachment is not appearing correctly within the browser extension. It doesn't even throw a generic decrypt error showing us an unusual case that maybe we didn't handle just yet.

The message contains 3 attachment (noname, encrypted.asc, public_key.asc) and rendered as:

Here is a short description of what I know about each attachment.

noname - it contains the detached signature
encrypted.asc - encrypted message
public_key.asc - public key of the sender

In comparison, this particular encrypted message can be decrypted on our android app very well.

The message originally came from msgsafe.io (another email service that supports PGP encryption).

Steps to reproduce:

1. I have saved the test message within our flowcrypt compatibility test account, just open the Test Email 2 with the label decrypt error and it should greet you with a similar problem.

Reference:
https://mail.google.com/mail/u/2/#inbox/FMfcgzGpFWLJPNQQFZcBjxKVTTCnMDWT

[martgil]

Update - it looks like this issue no longer exists upon re-checking the email that was supposed to reproduce the issue.
Test Email -
https://mail.google.com/mail/u/flowcrypt.compatibility@gmail.com/#inbox/WhctKKXXDrVfkVHmrlnlstsTXsPBRvXsVRgQsQKhrBCQKDDzmvnDRCltqJQtFbZHJnPVctb

closing this one -- if the problem persist, please kindly re-open or file a new Github issue. thanks

[martgil]

Re-opening the issue... building the latest version and refreshing the extension doesn't work quite well sometimes. I tried to check it once and against a freshly new build and in fact, it doesn't work and throws the original problem reported above.

One thing I noticed is that, when viewing the encrypted message on the web extension page (direct message read via message parameter) , the message works fine. But the problem exists when viewing the same encrypted message on the Gmail web app (via msgId) -- reproducible on the latest master branch.

I'm now checking if the problem exists on the older versions and will check why should I have previously been able to read them via Gmail in the past day.

[martgil]

parsed mime message (encrypted + unsigned message):