E2E Encryption Request Keys not updating when received

Description:

If you was added to a e2e encrypted room by other user you should request the keys and some online user should provide this room key to you, when you receive this e2e key you should be able to read decrypted messages and send encrypted messages, but it's working only after a client reload.

Steps to reproduce:

User A and B.

1. Create a e2e encrypted room using user A.
2. Send some messages to this room.
3. Add the user B to this room while user A is online.
4. User B receive the E2EKey of this room.
5. All encrypted messages are blank and you're not able to send new messages using user B.

Expected behavior:

You should be able to read and send messages to this room as soon as the E2EKey of this room was received.

Actual behavior:

You aren't able to read or send messages before reload the client.

Server Setup Information:

• Version of Rocket.Chat Server: 3.6.0-rc.0
• Operating System: N/A
• Deployment Method: N/A
• Number of Running Instances: N/A
• DB Replicaset Oplog: N/A
• NodeJS Version: N/A
• MongoDB Version: N/A

Client Setup Information

• Desktop App or Browser Version: Browser Version
• Operating System: MacOS / Brave

Additional context

Relevant logs:

Start by reproducing the listed User A/User B flow in a browser: receive the E2E key, inspect the client’s key-receipt behavior, and compare it with a reload. Done means encrypted history becomes readable and new encrypted messages can be sent immediately after the key arrives, without reloading.