Closed Mohitur669 closed 1 year ago
socketRef.current.on(ACTIONS.DISCONNECTED, ({ socketId, username }) => {
if(username){
toast.success(`${username} left the room`);
setClients((prevClients) => {
return prevClients.filter(client => client.socketId !== socketId);
});
}
});
The issues are fixed after applying the above patches.
Code is not running? Socket connection failed. Try again is there what to do
Code is not running? Socket connection failed. Try again is there what to do
This is the latest working code provided on github. You need to follow the steps given in readme. Don't you forgot to run server and client. P.S: This whole code is tested only locally.
After creating and joining the room, sometimes later a popup says "Socket connection failed" and the room closes automatically, how can I resolve the problem?
After creating and joining the room, sometimes later a popup says "Socket connection failed" and the room closes automatically, how can I resolve the problem?
Are you testing this in localhost?
yes I'm testing in local host
use npm instead of yarn
thanks I'll try
same error occured
same error occured
The problem is occurring because you have to run node server.js
and npm start
into different terminals. Both should be running at the same time.
i have tried bro but still same problem
sent you a connection req in LinkedIn .. message a google meeting link there
How did you implemented synchronization of code? Did you use OT libraries like ShareDB, OT.js?
Known Bugs
Note: The number of toast notification increases more and more if more users join and leaves the room.
Note: If you find any other bugs, please let me know. I will try to fix it as soon as possible :) In case you want to fix it yourself, feel free to make a pull request.