I've taken a while to setup quest automation as part of our build
process as a sanity test with end to end functionality. The test works
by pushing apk to device and then running a scene that teleports around
and does a few things without the need fo...
I was working on full end to end testing and having our quest builds run
on hardware as part of our CI/build process. The tests/apk won't run if
the screen isn't on. I came up with the following solution as a
workaround but this is more of a fun hack...
Turns out the disabling Experimental Features-> Hand Tracking resolved
this issue. I disabled it yesterday after a recommendation from a dev
and triggered a few builds with the batteries out of the controllers