From a45de2f13244b95da89f2c7aea9741db1c53efc6 Mon Sep 17 00:00:00 2001
From: Florian Duros <florian.duros@ormaz.fr>
Date: Thu, 28 Nov 2024 14:10:41 +0100
Subject: [PATCH 1/2] Remove deprecated calls in `webrtc/call.ts`

---
 src/webrtc/call.ts | 21 ++++-----------------
 1 file changed, 4 insertions(+), 17 deletions(-)

diff --git a/src/webrtc/call.ts b/src/webrtc/call.ts
index c2b24cadb82..29919137657 100644
--- a/src/webrtc/call.ts
+++ b/src/webrtc/call.ts
@@ -631,19 +631,17 @@ export class MatrixCall extends TypedEventEmitter<CallEvent, CallEventHandlerMap
         if (!this.client.getUseE2eForGroupCall()) return;
         // It's possible to want E2EE and yet not have the means to manage E2EE
         // ourselves (for example if the client is a RoomWidgetClient)
-        if (!this.client.isCryptoEnabled()) {
+        if (!this.client.getCrypto()) {
             // All we know is the device ID
             this.opponentDeviceInfo = new DeviceInfo(this.opponentDeviceId);
             return;
         }
-        // if we've got to this point, we do want to init crypto, so throw if we can't
-        if (!this.client.crypto) throw new Error("Crypto is not initialised.");
-
         const userId = this.invitee || this.getOpponentMember()?.userId;
 
         if (!userId) throw new Error("Couldn't find opponent user ID to init crypto");
 
-        const deviceInfoMap = await this.client.crypto.deviceList.downloadKeys([userId], false);
+        // Here we were calling `MatrixClient.crypto.deviceList.downloadKeys` which is not supported by the rust cryptography.
+        const deviceInfoMap = new Map();
         this.opponentDeviceInfo = deviceInfoMap.get(userId)?.get(this.opponentDeviceId);
         if (this.opponentDeviceInfo === undefined) {
             throw new GroupCallUnknownDeviceError(userId);
@@ -2516,18 +2514,7 @@ export class MatrixCall extends TypedEventEmitter<CallEvent, CallEventHandlerMap
                     return;
                 }
 
-                await this.client.encryptAndSendToDevices(
-                    [
-                        {
-                            userId,
-                            deviceInfo: this.opponentDeviceInfo,
-                        },
-                    ],
-                    {
-                        type: eventType,
-                        content,
-                    },
-                );
+                // Here we were calling `MatrixClient.encryptAndSendToDevices` which is not supported by the rust cryptography.
             } else {
                 await this.client.sendToDevice(
                     eventType,

From 9c4f21b3cb51f73f7373cf867801cb8fcb3e1109 Mon Sep 17 00:00:00 2001
From: Florian Duros <florian.duros@ormaz.fr>
Date: Fri, 6 Dec 2024 09:54:10 +0100
Subject: [PATCH 2/2] Throw error when legacy call was used

---
 src/webrtc/call.ts | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/src/webrtc/call.ts b/src/webrtc/call.ts
index 29919137657..99bce1e0074 100644
--- a/src/webrtc/call.ts
+++ b/src/webrtc/call.ts
@@ -2514,7 +2514,9 @@ export class MatrixCall extends TypedEventEmitter<CallEvent, CallEventHandlerMap
                     return;
                 }
 
-                // Here we were calling `MatrixClient.encryptAndSendToDevices` which is not supported by the rust cryptography.
+                // TODO: Here we were sending the event to the opponent's device as a to-device message with MatrixClient.encryptAndSendToDevices.
+                // However due to the switch to Rust cryptography we need to migrate to the new encryptToDeviceMessages API.
+                throw new Error("Unimplemented");
             } else {
                 await this.client.sendToDevice(
                     eventType,