https://livekit.io logo
Join Slack
Powered by
This message was deleted.
# helpdesk
s
This message was deleted.
m
It’s good to hear you have a repro. cc @eager-raincoat-52616 for follow up questions.
d
@eager-dentist-81563 do you have logs from these users? Can you send us a couple of example session URLs?
e
@eager-raincoat-52616 thanks for the reply, and apologies for the delay. here’s an example session url: https://cloud.livekit.io/projects/p_1eeobbhm3tg/sessions/RM_AxjF3UizeFy8 On the client side, I’m seeing “could not connect PeerConnection after timeout”
Here’s another example: https://cloud.livekit.io/projects/p_1eeobbhm3tg/sessions/RM_YZDhQFjpwjaq In this one, user 
KXHf5uukd3SKEXRVSD1URwKwTPP2
is the one with the issue. At the end they were able to connect when they switched back to wifi, but they were unable to connect until then when they were on mobile data.
d
thanks for sharing Sruli, just to confirm: can the user connect from our web client? I.e. if they can connect from https://meet.livekit.io
e
Thanks @eager-raincoat-52616 both users are in the US and are not online at the moment. I will check today and get back to you. Thanks 🙏
Oops, david. sorry dL…
@dry-elephant-14928 I tried this out with an affected user. He was able to see himself. However, if I joined first, he was unable to see me when he joined. If he joined first, he was able to see me when I joined. This was reproduce-able consistently as we were testing.
d
to confirm, this user is connecting on mobile / cellular network?
e
that’s correct
d
I think him not able to see you might be a bug with the application on mobile. As long as he's able to see himself, that means he's indeed able to connect to LiveKit Cloud from cellular networks. The issue seems to be with react-native somewhere
we'll investigate.. we may need to add additional logging on the server side to track this down a bit better.
e
okay, cool. Thank you. Let me know if you need anything from me.
@dry-elephant-14928 I’ve confirmed that this happens when there are two sim cards on the device. Both affected users have two sim cards on their device. We tested with them removing one of them and they were able to connect to the session.
d
Hey Sruli! I really appreciate the update! Wow.. this is bizarre.. I guess this may be a difference between web browser vs native webrtc on how it handles dual sim devices. we should test this use case with our RN client.
e
Thanks @dry-elephant-14928 🙏
Hey @dry-elephant-14928. Do you know if there’s been any movement on this? I’m learning about more users affected by this issue, and there must be others I do not know about. It’s the main issue we’re experiencing with Livekit. To the extent that when someone reports that they are unable to connect to calls, I immediately ask if they are (a) on a dual sim device and (b) on data. And that’s usually it. Thanks 🙏
d
hey @eager-dentist-81563 sorry we haven't been able to track this down. It's on our list of high priority issues tho. We'll spend some time on it this week and well keep you posted.
e
awesome, thank you 🙏
e
@eager-dentist-81563 we’re working on getting some dual sim devices to test this against, would you happen to have any examples of known devices it fails on? Just want to make sure we don’t run into a rare dual sim device where it does somehow work
e
Hey @eager-raincoat-52616 I just reached out to some users. I’ll let you know when I hear back from them. Thanks 🙏
@eager-raincoat-52616 just heard back from one user: iPhone 13 / iOS 16.2
Also iPhone 11 Pro / iOS 16.2
e
hmmmm if it’s iOS only specifically, looks like it’s this issue: https://bugs.chromium.org/p/webrtc/issues/detail?id=10966
there’s a field trial that seems to have fixed this in 2021 but they haven’t turned it on by default yet
can you try putting this in your AppDelegate.m:
Copy code
#import <WebRTC/RTCFieldTrials.h>

- (BOOL)application:(UIApplication *)application
    didFinishLaunchingWithOptions:(NSDictionary *)launchOptions {
  NSDictionary *fieldTrials = @{kRTCFieldTrialUseNWPathMonitor : kRTCFieldTrialEnabledValue};
  RTCInitFieldTrialDictionary(fieldTrials);
  /* ... */
}
e
yes it seems to be iOS specific. I’m not aware of any instances on Android.
Yes, I can add that
I just tested this out with one user and it seems to be working. Going to be doing a bit more testing today. Thanks so much 🙏
@eager-raincoat-52616
🙌 3
@eager-raincoat-52616 @dry-elephant-14928 tests seem to be holding up. Just released a new version with the fix. Thanks for your help.
d
Thank you @eager-dentist-81563 for the report and validating the fix! It would have been really difficult for us to track this one down without your help
🙌 1
🙏 1
➕ 1
e
That's awesome! Thanks so much!
🙏 1
2 Views
Open in Slack
PreviousNext
Powered by