You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
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.
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.
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
Used Package Manager
npm
Logs
No response
Validations
The text was updated successfully, but these errors were encountered: