Waiting for the application to run for 5 seconds before testing begins...
Starting test...
Sending a request to quit...
Failed to receive a call for ovr_Destroy on attempt to quit in 30 seconds '''
I am 100% positive that my game is quiting gracefully. When manually testing the quit behavior from both the Oculus Home "return to menu" and Rift Core 2 Oculus Dash quit, my game promptly quits. I can confirm that Application.Quit() is being called in OVRManager.
I'm uncertain about ovr_Destroy because I am using Unity and assuming that it is being called under the hood.
How serious of a failure is this and would it prevent a successful submission to the Oculus Store?
I am using Unity 2018.1 and OVRPlugin 1.25 . It should just work as long as Application.Quit is called in response to the events which is happening in OVRManager which I haven't changed.
I am using Unity 2018.1 and OVRPlugin 1.25 . It should just work as long as Application.Quit is called in response to the proper events, right? That is what is happening in OVRManager which I haven't changed.
Hi @juanoldinho. It's late August now and we're having this issue, too. Has there been any resolution? We are certain our application is exiting gracefully to Oculus Home. All of our exits happen via Application.Quit() in Unity.
I'm using the C++ SDK and having the same problem. This is the output I get from the VRC Validator:
Starting TestAppShouldQuit Waiting for the application to run for 5 seconds before testing begins... Starting test... Sending a request to quit... Failed to receive a call for ovr_Destroy on attempt to quit in 30 seconds Please refer to VRC Guidelines: https://developer.oculus.com/distribute/latest/concepts/vrc-pc-input-4/ Cleaning up... Test FAILED
My program exits instantly once "Sending a request to quit" is printed. appears The total wall clock time from that point to "Test FAILED" being printed is well under 1 second and I can confirm, thanks to logging in my own code, that ovr_Destroy is definitely being called in that time.
I've tried running the VRC Validator as Administrator; this didn't make any difference.
The program exits cleanly if I follow the manual steps described for VRC.PC.Input.4
Hi, sorry for the slow reply. I haven't uploaded my program to the store or created an appid for it yet, I've just been running the VRC Validator locally (using an appid borrowed from the Avatar SDK's Mirror sample for testing purposes).
