We've been following the guide and batch scripts closely, using a Quest 2 in Developer Mode, but no .autodriver file is ever generated during recording, despite no errors in ADB or logcat.
Multiple developers across the community have reported the same issue, which seems to affect all newer firmware versions for Quest 2 (and likely Quest 3/Pro as well). This is blocking our ability to automate E2E testing using on-device input replay - a feature that was core to AutoDriver’s value.
Could you confirm: 1. Whether AutoDriver is still supported on current Quest 2 OS versions? 2. If it’s deprecated or broken, whether there's a timeline for a fix or update? 3. Any official workarounds (beyond the XR Simulator)? We would really value clarification on this, or even confirmation that the team is aware of the issue.
It's a fantastic feature and would be great to see it functioning again.
In order to get this looked into, we would just like to inform you of our developer support center. On here, we have many resources that you may find useful in your Journey to making the future of the Metaverse!
