Skip to content
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

RTCPeerConnectionIceEvent.candidate always null, can't fire "ice-candidate" socket event #18

Open
fakhripraya opened this issue Nov 13, 2022 · 1 comment

Comments

@fakhripraya
Copy link

hi chaim

i followed your tutorial and the video chat seems to not appearing for the other end
i suspect it happened because the e.candidate on handleICECandidateEvent always null

function handleICECandidateEvent(e) { console.log(e) if (e.candidate) { console.log(e) const payload = { target: otherUser.current, candidate: e.candidate, } socketRef.current.emit("ice-candidate", payload); } }

i keep getting null on e.candidate property whenever the onicecandidate event fired,
the code is exactly simillar to what is in the tutorial, what am i missing?

@fakhripraya
Copy link
Author

it seems like the browser i used was the problem, i used google chrome v107

i tested this on mozilla and it worked, i saw your video using chrome, maybe its because the current version of the chrome don't support the current webRTC API yet

some said we need SSL in order for it to work, haven't tested it but ill test it later and update here

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

No branches or pull requests

1 participant