Forum Discussion
AutoDriver - Our E2E testing is no longer working
We were using AutoDriver, found here: https://developer.oculus.com/documentation/unity/ts-autodriver/
This no longer seems to work. The command that causes issues is: "adb shell debug.oculus.autoDriverApp". This will always return: "/system/bin/sh: debug.oculus.autoDriverApp: inaccessible or not found". This has seriously affected our testing, as we used this system for our E2E testing.
If anyone has information on this issue, good or bad, please reach out. My team is small and heavily relied on this system.
3 Replies
Replies have been turned off for this discussion
I want to use Auto Driver too. Though I could setprop the three statements with bat file, AutoDriver can not start and does not make default.autodriver file.
I guess AutoDriver does not start because of a lack of enviroment. By the below link, AutoDriver is delong on VrApiLayers. What is VrApiLayer? Which files need to install in oculus Quest2 ?
Please help me.
https://developer.oculus.com/documentation/unity/ts-autodriver/
https://developer.oculus.com/downloads/package/autodriver-batch-files/
...>adb.exe shell setprop debug.oculus.vrapilayers AutoDriver>adb.exe shell setprop debug.oculus.autoDriverApp xyz.skybox.player.ovr>adb.exe shell setprop debug.oculus.autoDriverMode Record>adb.exe shell getprop | findstr debug...[debug.oculus.autoDriverApp]: [xyz.skybox.player.ovr][debug.oculus.autoDriverMode]: [Record][debug.oculus.vrapilayers]: [AutoDriver]...
adb.exe pull /sdcard/Android/data/xyz.skybox.player.ovr/AutoDriver/default.autodriver MyRecord.autodriver
adb: error: failed to stat remote object '/sdcard/Android/data/xyz.skybox.player.ovr/AutoDriver/default.autodriver': No such file or directoryHey there. We had similar issues and I just found out that you need ARM64 as an architecture to have autodriver run. This happened after a specific firmware update (I think it was around 44v-47v). Did you find anything related to this?
Dear All,
I had same issue. Could you guide me on how to solve the issue?
If the issue is due to ARM64 architecture, could you share how to solve the architecture issue?
