Upgrading from polling to webtransport will report engine invalid WebTransport handshake. about engine.io HOT 8 CLOSED

  send accept ranges +0ms
  send cache-control public, max-age=0 +0ms
  send modified Fri, 04 Aug 2023 06:56:42 GMT +0ms
  send etag W/"5f3-189bf558e3d" +0ms
  send content-type application/javascript +0ms
  send not modified +0ms
  engine intercepting request for path "/engine.io/" +10m
  engine handling "GET" http request "/engine.io/?EIO=4&transport=polling&t=Oc_Oe50" +0ms
  engine applying middleware n°1 +0ms
  engine handshaking client "MKuE7QAV04RAXQT5AAAB" +1ms
  engine:transport readyState updated from undefined to open (polling) +10m
  engine:socket readyState updated from undefined to opening +3s
  engine:socket readyState updated from opening to open +1ms
  engine:socket sending packet "open" ({"sid":"MKuE7QAV04RAXQT5AAAB","upgrades":["webtransport"],"pingInterval":25000,"pingTimeout":20000,"maxPayload":1000000}) +0ms
  engine:polling setting request +10m
  engine:socket flushing buffer to transport +0ms
  engine:polling writing "0{"sid":"MKuE7QAV04RAXQT5AAAB","upgrades":["webtransport"],"pingInterval":25000,"pingTimeout":20000,"maxPayload":1000000}" +0ms
  engine:socket executing batch send callback +1ms
  engine:transport readyState updated from open to closed (webtransport) +16ms
  engine:socket readyState updated from open to closed +15ms
  engine:webtransport error while reading: undefined +3s
node:internal/process/promises:288
            triggerUncaughtException(err, true /* fromPromise */);
            ^

[UnhandledPromiseRejection: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason "0".] {
  code: 'ERR_UNHANDLED_REJECTION'
}

Node.js v18.17.0