toast-notification-count issue

[Mohitur669]

Known Bugs

• If a user leaves or enters the room, the toast notification number not showing correctly.
  
  • Like, if I (user1) create a room and user2 joins the same room, then instead of one toast notification, four toast notifications are shown.
  • Now if the user2 leaves, then two toast notifications are shown instead of one.

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.

[Mohitur669]

1. To solve the toast notification count remove the React strict app component, just normally pass the component in the index.js
2. After solving that issue an undefined object is showing up on the connected users' screen if a user leaves. To solve this create a check for undefined users like this,

   socketRef.current.on(ACTIONS.DISCONNECTED, ({ socketId, username }) => {
   if(username){
       toast.success(`${username} left the room`);
       setClients((prevClients) => {
           return prevClients.filter(client => client.socketId !== socketId);
       });
   }
   });

[Mohitur669]

The issues are fixed after applying the above patches.

[dilpreetkaur03]

Code is not running? Socket connection failed. Try again is there what to do

[Mohitur669]

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.

[monishsoorya31]

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?

[Mohitur669]

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?

[monishsoorya31]

yes I'm testing in local host

[Mohitur669]

use npm instead of yarn

[monishsoorya31]

thanks I'll try

[monishsoorya31]

[monishsoorya31]

same error occured

[Mohitur669]

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.

[monishsoorya31]

i have tried bro but still same problem

[Mohitur669]

sent you a connection req in LinkedIn .. message a google meeting link there

[monishsoorya31]

https://meet.google.com/pko-einq-dvv

[rajatsharma979]

How did you implemented synchronization of code? Did you use OT libraries like ShareDB, OT.js?