Everything logged twice in gateway

[Polozone]

Hello socket-io community !

I read many subjects about my bug, but I can't find what I'm doing wrong.

My problem : Absolutely everything is logged twice in my gateway.
This is problematic, because all my events are triggered twice. So the app is not running correctly. I readed many things about that subject, and I :

• use socket.off in the return of my useEffect
• not registering the event handler in the connect event

Here is the piece of code that check if a client can connect to my gateway :
`

    onModuleInit() {
    this.server.use(async (socket, next) => {

        // return userId if token is valid
        const response = await this.authService.checkTokenValidity(socket.handshake.auth.token);

        if (response) {
            socket.data.userId = response;
            // Accept client
            next();
        } else {
            next(new WsException('invalid token'));
        }
    })
    this.server.on('connection', async (socket) => {
        this.joinRoomsForClient(socket.data.userId, socket);
        // print all clients connected to my gateway
        this.readMap();

        socket.on('disconnect', async () => {
            this.leaveRoomsForClient(socket.data.userId, socket);
        })
    });
}`

How I subscribe to my "message" event :

`
@SubscribeMessage('message')

async handleMessage(@MessageBody() data: Message, @ConnectedSocket() client: Socket): Promise<boolean> {

    let isSenderMuted: { isMuted: boolean, isSet: boolean, rowId: number };

    isSenderMuted = await this.chatService.isMute({channelId: data.channelId, userId: data.senderId});

    if (isSenderMuted.isMuted === true){

        return true ;

    }

    client.to(String(data.channelId)).emit("messageBack", data);

    return false ;
}

`

As I said, this handler is not inside the connect event.

Here how I use socket.on in client-side :

`
useEffect(() => {
socket.on("messageBack", messageEvent);

return () => {
  socket.off("messageBack", messageEvent);
};

}, []);
`

I'm using socket.off as I saw in many Q&A, to unsubscribe the event when my React components is "unmount".

I have only one emit on my "message" event in all my applications, and that one emit is called only one time, when I click a button to send a message.

Here is how I emit on client-side :
socket.emit("message", msgToSend, (response: boolean) => {...some code...}

I'm struggling to find my error, as the more generic response I saw for this issue was to

• use socket.off in useEffect's return
• not making my event inside the connection event

Something important to note :

• There is several gateway's in our app (3) => chat gateway (mine), game gateway (gateway of my friend who is part of the project), and a last one
• When my logged from chat gateway are printed twice, is BEFORE the log of chat gateway, and AFTER, here is an example if I add a log inside the middleware (to see who will connect)

1 is connecting... (chat gateway, mine)
socket map id = C9ixuhYBzQcCmKI7AAAB (game gateway)
1 is connecting... (chat gateway, mine)

disconnection log :
userId: 1 is disconnected from game gateway
userId: 1 is disconnected from chat gateway
userId: 1 is disconnected from chat gateway

After all, the main problem is when a client-1 send a message to a client-2, client-2 receive this message twice.

Another important things to note, If i change my "message" logic with that => (just adding some text to the message that the server will receive to send to others clients in the room)

`
@SubscribeMessage('message')

async handleMessage(@MessageBody() data: Message, @ConnectedSocket() client: Socket): Promise<boolean> {

    let isSenderMuted: { isMuted: boolean, isSet: boolean, rowId: number };

    isSenderMuted = await this.chatService.isMute({channelId: data.channelId, userId: data.senderId});

    if (isSenderMuted.isMuted === true){

        return true ;

    }

    data.content += " passed server side ";

    client.to(String(data.channelId)).emit("messageBack", data);

    return false ;

}

`

I can see of client side :
messageContent + " passed server side "
messageContent + " passed server side " + " passed server side "

I dont know if its clear, but its like the event "message" call back himself with the new message content (I added a string before emitting in the example).

I can't understand why everything is logged and trigger twice, as the logic of my friend on his gateway is very similar to mine.

If you need more information, feel free to ask, I'll update my post.

Thank you for your help, community !

[Polozone]

The problem was due to an error in importation of modules, nothing related to skcet-io