Skip to content

Handle ICE candidates with missing usernameFragment #181

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged

Conversation

samrat
Copy link
Contributor

@samrat samrat commented Dec 29, 2024

I ran into an error because flutter-webrtc(https://github.com/flutter-webrtc/webrtc-interface/blob/767eb083a9ee88a4e37b49cb70bb7831c7c2414d/lib/src/rtc_ice_candidate.dart#L6) doesn't seem to send this field.

The ICECandidate type spec already allows the field to be nil. This PR would also allow candidates where the usernameFragment field is not present at all.

@mickel8
Copy link
Member

mickel8 commented Dec 29, 2024

Thanks! I confirmed that usernameFragment indeed might be null according to RTCIceCandidateInit interface and procedure describing the creation of RTCIceCandidate object - link

@mickel8 mickel8 merged commit 7b96028 into elixir-webrtc:master Dec 29, 2024
@mickel8
Copy link
Member

mickel8 commented Dec 29, 2024

I slightly refactored the code in 117f39e

@mickel8 mickel8 mentioned this pull request Feb 7, 2025
63 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants