This message was deleted.

cc @freezing-lifeguard-43174

that event is triggered for you to handle, in case you'd like to display any UI to the user. If you are seeing issues with automatic reconnects, could you tell us what steps you've taken to reproduce it?

I have reproduced the issue and logged the reconnection process. The code used is the Flutter client example version 1.5.3. Testing device is a Vsmart running Android 11. Flutter version used is 3.13.5 with Dart 3.1.2.

Thanks for the video. it sounds like you were able to reproduce a failed auto reconnect. We'll take a look

ah, let me test it.

Hi, do you have any new information about this case?

yeah, I’m testing it

Great, I will continue testing. If there are any issues, I will update you.

I am bumping into a problem that sounds very much like this one. What is the ETA on release of the patch?

@silly-boots-13504, Looks like there’s a rendering exception, let me check.

@freezing-lifeguard-43174 The problem my customers are running into is associated with bad network connections. The user on a bad wifi will reconnect and other people in the room (on flutter running devices) may not reconnect to one or more of their publications and the person on bad wifi will frequently not reconnect to the audio publication of others in the room. I am not sure why there is an affinity for video in this case (or even if there is an affinity, though anecdotally it does seem that video recovers better in my testing). What may be obvious to you is that my Golang Livekit clients do not seem to have any audio reconnection issues (they do not subscribe to the video feeds). I found that I can easily reproduce this problem by setting up my network to drop between 35-50% of packets. I was unable to test your branch unfortunately because I get a build error. If you know how I can avoid that, I'd be very grateful to know it.

hey @silly-boots-13504, @bumpy-byte-87314, Fixed rendering exception.

Currently, the media stream is encrypted with AES 128. In the future, is it possible to change it to AES 256. Is there any parameter that allows me to change this encryption choice?

Hey Minh, where do you see the encryption mode being used?

Hi David, i see that on https://livekit.io/security

Hey @silly-boots-13504, maybe I'm the one misunderstanding! Can I ask what you are trying to ensure? Is it the media traffic or the signaling traffic? Do you have a certain requirement for certain kinds of encryption?

From what I understand, the signaling traffic refers to the transmission of events such as DataReceived, ConnectionQualityChanged, RoomMetadataChanged,... the media traffic includes both video and audio streams. Do I understand correctly? If I understand correctly, I need to encrypt both the media stream and signaling stream using AES 256 encryption. I know that the Flutter client SDK already provides encryption for the media traffic (if using e2eeOptions). However, I don't know which encryption method is being used by Livekit for both the media traffic and the signaling traffic

Signaling traffic is encrypted with TLS, so that depends on your HTTP server and how you choose to terminate TLS. Otherwise Media/data traffic goes over AES-GCM, by default that's 128 bits. If that's insufficient, as you pointed out, we support full end to end encryption as well

Does the media/data traffic have AES-GCM 256bits. Do you have plans to implement AES GCM 256-bit for the media/data traffic in the future?

we can definitely enable higher encryption. I'm mainly curious on your use case that would require it

I want to try AES-GCM 256-bit to test its performance with the media/data traffic because, in 2015, the NSA stopped recommending the use of 128-bit keys for AES encryption and started recommending 256-bit keys.

I see, this could be changed to use GCM 256bit. WebRTC supports these ciphers: https://stackoverflow.com/questions/72077469/change-cipher-in-webrtc/72079817#72079817