Waiting for this message, this may take a while.

Phone was updated from the latest stable riot-android to element via GPlay (no beta subscription)

Now all messages in all e2ee direct chats including new messages are: Waiting for this message, this may take a while.

After update the phone was verified via pitcture sequence with riot-web. All contacts are verified and has green point/shield on all devices, all contacts are on my own synapse instance (1.15.1-1 debian stable).

Cross-signing is enables, Keys are trusted, Private keys are not known:

I tried to clear cache and to restart phone without sucess.

[anoadragon453]

Hey all - thanks for sending in your reports. As a result, we noticed a serious regression in Synapse v1.38.0 which caused Element Android to have a significantly higher chance of running into decryption issues.

The issue is now fixed with Synapse v1.38.1, which was released on Thursday. The upcoming Synapse v1.39.0 will fix another long-standing encryption bug which could sometimes cause decryption issues on various clients, including Element Android. As these new versions are rolled out to the federation, encryption issues should become less and less frequent.

We’re still tracking down the edge cases though – as a reminder, the best way to help debug encryption issues when they pop up is to hit the “Submit Debug Logs” from settings (or shake your phone) on any devices that were affected. This allows us to get a clearer picture of why keys didn’t arrive or failed to send. Thanks!

[Wodann]

I’m consistently seeing this issue on my android phone (works fine in my desktop browser’s session) for the last message sent by one user. The moment they send more messages, the message that previously displayed the error will become visible, but the new latest message will report the error instead.

I’ve tried clearing the cache, but to no avail.