Robin de8b5d98ec [SDK] 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.

On the SDK this is RTCMember.backendIdentities, which the LiveKit backend matches media and data packets against; the harness keys its tiles by the membership id, which the backend identity no longer tells apart.

(cherry picked from commit c9aad2a2b3279782d101c9bc6c80af0417ccbb92)

2026-10-13 13:00:58 +02:00

..

index.html

Publish and unpublish on the local member

2026-10-08 13:53:57 +02:00

main.ts

[SDK] Match LiveKit participants against all backend identities

2026-10-13 13:00:58 +02:00

session.ts

sdk implementation

2026-10-08 13:53:56 +02:00