From 1700e9fe2076615b71dabd723403717968772a25 Mon Sep 17 00:00:00 2001 From: Robin Date: Tue, 13 Oct 2026 12:59:14 +0200 Subject: [PATCH] Match LiveKit participants against all backend identities A member authenticated through the legacy JWT endpoint publishes under a `user:device` identity, while one authenticated through the default endpoint publishes under a hashed identity. Both are listed in the membership's backend identities, so match against the whole list rather than only the primary one. Element Call's test membership mock, matching the SDK's RTCMember. --- src/utils/test.ts | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/src/utils/test.ts b/src/utils/test.ts index f59eecd7e..9bb92b3ba 100644 --- a/src/utils/test.ts +++ b/src/utils/test.ts @@ -224,7 +224,7 @@ export function mockRtcMembership( deviceId: string, customOverwrites?: { rtcBackendIdentity?: string; - /** Every identity the member may have in LiveKit, when more than one. */ + /** Every identity the member may have on its transport, where more than one. */ backendIdentities?: string[]; callId?: string; fociPreferred?: Transport[]; @@ -471,6 +471,7 @@ export function mockRTCMember( }; const base = { rtcBackendIdentity: membership.rtcBackendIdentity, + backendIdentities: membership.backendIdentities, userId: membership.userId, deviceId: membership.deviceId, memberId: membership.memberId,