You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Was not able to send any messages at all in an 'encrypted' room (dm) from particular sessions. Not sure exactly how it happened but android element showed encryption disabled for room (dm) despite my other sessions showing the room encryption as already enabled. Enabling encryption on android element showed "encryption enabled" room message on my other sessions as well, despite already showing encryption enabled since before.
I was able to send messages properly immediately once encryption from android was enabled. Only new sessions were affected by this, and were unable to send encrypted messages to such rooms. I have noticed on staging.element.io for sure but also develop.element.io and app.element.io if I recall correctly. I have had cross signing turned on and used recovery keys while logging in to all my new sessions, unlike my older session that I setup by connecting to backup in the privacy settings menu. I also had cross signing turned on and the backup connected the way mentioned, long ago.
Steps to reproduce
Not exactly sure since I don't want to disturb my setup again but I think connecting to backup via privacy settings between sessions with two different encryption options for the same room and then adding a new session but using recovery keys while logging in, is the culprit. I had cross signing enabled on all sessions so I'm guessing the conflicting information causes this error but I could be wrong. I'm not technically skilled in this to know, sorry for quality of report I had to make since I couldn't find similar issue mentioned. The original sessions with conflicting information both function as the room setting claims it works but new sessions don't. I had connected the backup and setup cross signing long ago and this might not be possible anymore.
Describe how what happens differs from what you expected:
To be able to send messages since the room is shown as encrypted with no indication of error other than "some of your messages have not been sent".
Logs being sent: yes
Version information
Platform: web (in-browser): staging.element.io as well as develop.element.io and app.element.io if I recall correctly
Based on your logs, it looks like someone redacted the encryption event in that room, which will have confused the clients since now they won't know what to do. Or in other words, I think this is a duplicate of element-hq/element-meta#1501 and we should fix #10618
Description
Was not able to send any messages at all in an 'encrypted' room (dm) from particular sessions. Not sure exactly how it happened but android element showed encryption disabled for room (dm) despite my other sessions showing the room encryption as already enabled. Enabling encryption on android element showed "encryption enabled" room message on my other sessions as well, despite already showing encryption enabled since before.
I was able to send messages properly immediately once encryption from android was enabled. Only new sessions were affected by this, and were unable to send encrypted messages to such rooms. I have noticed on staging.element.io for sure but also develop.element.io and app.element.io if I recall correctly. I have had cross signing turned on and used recovery keys while logging in to all my new sessions, unlike my older session that I setup by connecting to backup in the privacy settings menu. I also had cross signing turned on and the backup connected the way mentioned, long ago.
Steps to reproduce
Not exactly sure since I don't want to disturb my setup again but I think connecting to backup via privacy settings between sessions with two different encryption options for the same room and then adding a new session but using recovery keys while logging in, is the culprit. I had cross signing enabled on all sessions so I'm guessing the conflicting information causes this error but I could be wrong. I'm not technically skilled in this to know, sorry for quality of report I had to make since I couldn't find similar issue mentioned. The original sessions with conflicting information both function as the room setting claims it works but new sessions don't. I had connected the backup and setup cross signing long ago and this might not be possible anymore.
Describe how what happens differs from what you expected:
To be able to send messages since the room is shown as encrypted with no indication of error other than "some of your messages have not been sent".
Logs being sent: yes
Version information
For the web app:
The text was updated successfully, but these errors were encountered: