Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error when sending encrypted message #3792

Closed
MaxPower654 opened this issue Aug 4, 2021 · 11 comments · Fixed by #3804
Closed

Error when sending encrypted message #3792

MaxPower654 opened this issue Aug 4, 2021 · 11 comments · Fixed by #3804
Labels
A-E2EE T-Defect Something isn't working: bugs, crashes, hangs and other reported problems

Comments

@MaxPower654
Copy link

Describe the bug

After upgrading to 1.1.15, some android users are unable to send encrypted messages to a room with multiple members.
There is a error message like "Did not sent message, retry?"
Some 1:1 chats were also affected.
After rolling back to v.1.1.12 or using schildi.chat the issue was gone.

To Reproduce

Steps to reproduce the behavior:

  1. Send encrypted message to room
  2. See error

Expected behavior

I would expect the message to be encrypted and sent.

Screenshots

sendfail

Smartphone (please complete the following information):

  • Device: at least Pixel 4a
  • OS: Android 11

Additional context

  • 1.1.15 F-Droid and Google Play
  • Private Homeserver, v.1.37

From the behaviour, I would expect this issue to be a duplicate from element-hq/element-web#17195, but on android.
I already checked if the encryption event was redacted, but it seems to be fine.

@MaxPower654 MaxPower654 changed the title Error "Unable to send message 925 Error when sending encrypted message Aug 4, 2021
@voice06
Copy link

voice06 commented Aug 4, 2021

I can confirm I am seeing this issue as well with 1.1.15, I am not longer able to send encrypted messages, but I can from Web or Desktop.

@williamkray
Copy link

I had two users report this issue to me. they both reinstalled the application from scratch and it resolved the issue. I also have an android device and have not had this issue.

@MaxPower654
Copy link
Author

MaxPower654 commented Aug 4, 2021 via email

@delroth
Copy link

delroth commented Aug 5, 2021

I've hit the same issue today and have heard reports from at least two other people on two different encrypted rooms.

@miniature-igloo
Copy link

Many people on my server are having this issue. It's happening across many different encrypted rooms.

I've had them uninstall/reinstall & log out and log back in. Both of these work for a while, but the issue comes back.

It's limited to Android 1.1.15. Not happening for any of the people using iOS app, desktop app, or a release before 1.1.15.

@miniature-igloo
Copy link

I just checked to see if in the rooms that it is happening in had their 'm.room.encryption' events redacted. None of them did. None of the rooms on the server have had the 'm.room.encryption' event redacted.

@manuroe
Copy link
Member

manuroe commented Aug 6, 2021

The bug happens once you logged out from a device:

To reproduce it:

  • User A has 2 devices: A1 and A2
  • User B has B1 (having User B is probably not mandatory
  • A sends messages to a room with B
  • A logs out from A2

-> A cannot send messages from A1 anymore

@manuroe manuroe added T-Defect Something isn't working: bugs, crashes, hangs and other reported problems feature:crypto labels Aug 6, 2021
@pkern
Copy link

pkern commented Aug 6, 2021

For what it's worth, I did not log out anywhere and still got that persistent error on Android. It just suddenly started yesterday, not even directly connected with an app update.

@manuroe
Copy link
Member

manuroe commented Aug 6, 2021

For what it's worth, I did not log out anywhere and still got that persistent error on Android. It just suddenly started yesterday, not even directly connected with an app update.

thanks @pkern. There might be another issue. Can you rageshake mentioning this issue (3792), please?

@onurays
Copy link
Contributor

onurays commented Aug 6, 2021

For what it's worth, I did not log out anywhere and still got that persistent error on Android. It just suddenly started yesterday, not even directly connected with an app update.

It is happening even if other users log out. I am preparing a release including the fix.

@miniature-igloo
Copy link

What is the expected timeline to get this fix onto Google Play? This has crippled my server.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-E2EE T-Defect Something isn't working: bugs, crashes, hangs and other reported problems
Projects
None yet
Development

Successfully merging a pull request may close this issue.

9 participants