Forum Discussion

🚨 This forum is archived and read-only. To submit a forum post, please visit our new Developer Forum. 🚨
Jonathan123ii's avatar
Jonathan123ii
Honored Guest
2 years ago

Unable to inspect quest pro's browser

Hi! I'm honestly going insane over this, I've been wanting to get a proper workflow into developing my XR game using Godot.

What I'm currently doing is, Godot initializes a webserver with TLS enabled (though I don't have a certificate for it so it throws a bunch of certification errors) on port 8060 on my computer. I also bind it to the IP address of my computer (192.168.1.245).

The browser loads the page as intended by putting in 192.168.1.245:8060, yay, but when I go to chrome://inspect and look at my device list, quest pro is seen in the list, however there is no prompts for debugging.

I've tried using `adb kill-server` to see if its ADB conflicting with chrome but that hasn't changed anything.

I'm unsure on how adb reverse works exactly but even if I call `adb reverse tcp:8060 tcp:8060` it still has no impact.

 

I just need some help regarding this. Dev mode is enabled, I have development hub connected, still doesn't work if I don't use it. Does anyone else have the same problem with these steps, am I missing something?

Any setups or guides which have a different process on debugging with the browser would be so helpful, for right now though I guess I'll have to use virtual desktop/link just to debug my game.

No RepliesBe the first to reply