This message was deleted.
# helpdesk
s
This message was deleted.
t
What SDK are you using? In our Flutter app, Firefox calls also fail with 'Failed to connect to server.' And since we're using LiveKit cloud, I can't tell whether this is SDK issue or server one.
h
Hello @thousands-london-83216 It’s client-sdk-js@1.5.0 livekit-server@1.3
Both livekit.io/playground and example.livekit.io produce the same issue.
b
I am facing a similar issue using the example.livekit.io. Livekit is not working on Safari mobile. Given 2 users, one using Chrome desktop, and another using Safari mobile: The user on mobile is able to see the video from chrome desktop, but Desktop can't see any video from Safari Mobile I am using Safari 16.1
d
@high-exabyte-20673 to be clear, you are saying FF/Safari doesn't work for that particular user, but it does work for you? Both FF and Safari are working perfectly fine for us. They are supported browsers.
the logs you sent do not include the fields. could you enable them and send over the new logs for when that participant couldn't connect? in particular this line is useful:
rtc/transport.go:1357   ice candidates
@thousands-london-83216 you are likely speaking of a different issue. could you open an issue under client-sdk-flutter repo? 🙏 Please include as much information as possible in order to help us to reproduce it.
1
@bulky-animal-7027 I believe you are seeing something different. Could you start a new thread please? Screenshots would be helpful there.
t
@dry-elephant-14928 You're right since it only fails in Flutter sdk and not the react one. https://github.com/livekit/client-sdk-flutter/issues/219
🙏 1
h
@dry-elephant-14928 Yes, it doesn’t work for that particular user. On my side it works with no issues. I attached logs filtered by participants.
@dry-elephant-14928 I was able to get some fresh logs both from server and firefox:
Is there anything else I could configure on client or server side to gather more info about the issue?
d
Hey @high-exabyte-20673 we are tracking this one and believe it's related to this issue. The team is investigating now
h
I’ll take a look. Thanks for letting me know @dry-elephant-14928!
@dry-elephant-14928 I build a docker image to try out the fix for this issue but it didn’t help. I attached more info in https://github.com/livekit/livekit/issues/1060