Vite server ends up in a infinite reload loop when used with usb remote debugging on Android with chrome://inspect

[darktears]

Describe the bug

I have a vite project working perfectly fine on my desktop. Now I try to debug it on my phone using the remote debugger of chrome. I head to chrome://inspect, forward the port 3000 and then on the phone I can successfully load the website (so the port forwarding work just fine) but then vite server enters into a reloading loop and I have no idea why as a user. It seems some connection is lost (likely that hmr stuff) but there is no actionable feedback or useful debug since the debug output gets cleared because the page is reloaded. I think a 4s timeout would already help any developer to gather some log before everything is cleared up. Finally I'm kind of sure that I need to forward more ports than 3000 but it's not explained anywhere in the doc if that's the case.

Anybody ever tried to debug a vite app on a phone through USB?

Reproduction

https://github.com/foldable-devices/demos/tree/master/starfold

System Info

Windows, Android device, Chrome.

Used Package Manager

npm

Logs

No response

Validations

• Follow our Code of Conduct
• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to https://github.com/vuejs/vue-next instead.
• Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
• The provided reproduction is a minimal reproducible example of the bug.

[ygj6]

See if this #4259 can help you.

[darktears]

Nothing worked me. Disabling hmr also doesn't work and the page keeps reloading.

[darktears]

At this point I don't mind reloading manually, is there any workaround to have the server just serve the page and that's it?

[sapphi-red]

@darktears I was not able to reproduce (windows chrome + android).
Does it still happen?

It reproduced when I set server.hmr.port to a port which is not forwarded. So it might happened by that for some reason.

[timothyallan]

FWIW I still have the exact same issue on my iOS devices using Charles Proxy. Nothing in the other infinite reboot threads have helped, including disabling hmr. Works great on all my desktop browsers.

[sapphi-red]

This might be because a port was forwarded to a different port. #8650 covers this case.
Closing this issue for now. Please try 3.0.0-beta.1.