Unjustified "transport close"

[sema-fedotov]

Good afternoon, everyone. At the moment, I am developing a React application. I use React and node.js and socket.io (in conjunction with the socket. io-client, both have a 4.2.0 version). I ran into the following problem: clicking the button triggers a click on the link
window.open("LINK", "_blank")

Code on the client:

import io from 'socket.io-client'
const socket = io('LINK', {
  transports: ['websocket', 'polling']
})

Code on the server

import { Server as Socket } from 'socket.io'
const io = new Socket(http, {
  cors: {
    origin: "*",
    methods: ["GET", "POST"]
  }
})

But as soon as the link opens, the client loses connection to the server. The server receives the "disconnect" event due to "transport close", and the client receives the "disconnect" event a little later due to "ping timeout".

I also want to clarify that the problem does not manifest itself when exiting the application (for example, when clicking on a notification on a smartphone), after returning to the application everything functions as it should.

Everything works fine, except that the connection is lost.

But I solved the problem by switching to the version of one of my old projects (2.3.0). What could be the problem with version 4.2.0?