EiOS can sometimes send unencrypted messages in encrypted rooms

[Twi1ightSparkle]

Steps to reproduce

I don't know how to trigger this in the first place. But when it happens, just go to the affected room and send a message

Outcome

What did you expect?

• The message to be encrypted
• The room name/icon to show

What happened instead?

The room appear to be missing some state resulting in:

• The iOS app thinks the room is not encrypted and sends unencrypted events
• The room icon is not displaying
• The iOS app shows the canonical alias as the room name instead of the actual name

I did a rageshake, then cleared cache. The room is now behaving.

As this is an internal room, the linked rageshake has a screenshot and the room ID

Your phone model

iPhone 11 Pro Max

Operating system version

iOS 15.1

Application version

Internal TestFlight Build v1.6.8 #20211117180457

Homeserver

twilightsparkle.dev

Will you send logs?

Yes

[JonasKress]

Does the room appear to be 'unencrypted' in the UI for you?

[Twi1ightSparkle]

Does the room appear to be 'unencrypted' in the UI for you?

Yes. I attached a screenshot in my linked rageshake

[ShadowJonathan]

I just had the same problem, noted, the room was created inbetween me creating it on desktop, and me opening the room via a notification.

Despite the room not being marked as encrypted, it did decrypt messages from it, it only did not encrypt messages back

[BillCarsonFr]

I just had the same problem, noted, the room was created inbetween me creating it on desktop, and me opening the room via a notification.

Despite the room not being marked as encrypted, it did decrypt messages from it, it only did not encrypt messages back

Hello @ShadowJonathan Do you also notice other issues with the room, like missing topic? missing room name? missing admin?

[ShadowJonathan]

These are DMs, so there's no topic or room name. However, in the rooms where this happens, i dont see any user as "admin", yes.

It also doesnt say "messages here are end-to-end encrypted".

I'll clear cache.

[ShadowJonathan]

After a clear-cache, it correctly resolved the room for me again.

I started talking to this particular user without this device being online for a while, i think it can either be a bug in;

• iterative offline sync (in an "extension" part doug mentioned)
• synapse's sync excluding events
• eios's sync in general, detecting gappy state sync

[BillCarsonFr]

Fixed by matrix-org/matrix-ios-sdk#1358
Doesn't protect against the state reset, but it wouldn't revert encryption

[BillCarsonFr]

https://github.com/matrix-org/element-ios-rageshakes/issues/12797

[BillCarsonFr]

@Anderas can you have a look at the previous RS to see if you see why m.room.encryption got reverted?

[Anderas]

https://github.com/matrix-org/element-ios-rageshakes/issues/15702
https://github.com/matrix-org/element-ios-rageshakes/issues/18461

[Anderas]

The loss of encryption was likely related to general loss of room state reported in many rageshakes. Since implementing a fix for missing / corrupted room state there have (thus far) been no new reports of missing room names or unencrypted rooms.

If reported again, the rageshakes will include some extra logs that should help with identifying the root cause.

[lyczak]

I've encountered what I believe to be this same issue on Element iOS, version 1.8.27.
I created an E2E room on Element Desktop on Mac, version 1.11.3 and was trying to send messages in the same E2E room from Element iOS.
Element iOS reported that encryption was disabled for the room. Although encrypted messages that had been sent from Element Desktop were visible in Element iOS, any new messages sent from iOS were sent unencrypted. In room settings, the Encrypted option on Desktop was enabled while it was disabled on iOS. Attempting to enable it on iOS resulted in the app freezing with a loading symbol until the operation was canceled or the app was restarted.
This problem was fixed by clearing the cache on Element iOS.
This issue shows some similarities to Element-Web Issue #21729 which I also commented on.

[pixlwave]

@lyczak Did you send a rageshake for the issue?

[lunasophia]

This is still happening for me, and is presenting in the same way with the same resolution. Element iOS version 1.11.18. I see there's now a 1.1.19 (released 2h ago) and am updating presently; will report back if I see the issue again.