Forum Discussion
Reserved Interactions Test fails (back button and volume buttons work as requested)
In our beta tests using Gear VR, the back button and volume buttons work as requested. But when submitted to review, the "reserved interactions test" fails with the following message:
A back button long-press (greater than 0.75 seconds) must bring the user to the Universal Menu.
A “back” action is interpreted by the application dependent on its current state, but generally it will retreat one level in an interface hierarchy. The short-press should provide a custom confirmation dialog which allows the user to exit the app and return to Oculus Home.
Your volume buttons must adjust the volume using the VR volume UI provided by the Oculus Mobile SDK. Currently, your volume display does not function as expected.
More information about the Oculus Mobile SDK is available here: https://developer.oculus.com/documentation/mobilesdk/latest/concepts/book-intro/
Our application does not have any specific handlers for the back action or the volume button actions, other than the defaults described above.
How can we proceed?
How can we proceed?
19 Replies
Replies have been turned off for this discussion
- We are using version 1.10.0 with Unity 5.4.1 and buttons work automatically as expected. We tested. But we still get the "reserved interactions test" failed in the review phase.
- Updated to 5.5 and submitted again for a review. Again, everything works fine on our side of the tests. Thank you.
- Got a similar response, about home and volume buttons not working properly. All mentioned buttons do work fine on our side (just as described in the response). We even tested in one of the mentioned phones (Samsung S6) in the review response.
Rebuilt and sent again now. What should we do? - No trace of either libOculusPlugin.so or libOVRPlugin.so.
- OVRPlatformMenu script attached to the Camera.
- OVR related scripts in Assets folder:
Android/assets/oculussig_...oculussig_...oculussig_...OVRGamepad.bundlex86/OVRGamepad.dllx86_64/OVRGamepad.dll
Assets/OVR/Scripts/OVRBoundary.csOVRCameraRig.csOVRCommon.csOVRDebugHeadController.csOVRDisplay.csOVRHaptics.csOVRHapticsClip.csOVRInput.csOVRManager.csOVROnCompleteListener.csOVROverlay.csOVRPlatformMenu.csOVRPlugin.csOVRProfile.csOVRTouchpad.csOVRTracker.csUtil/OVRChromaticAberration.csOVRCubemapCapture.csOVRDebugInfo.csOVRGridCube.csOVRModeParms.csOVRMonoscopic.csOVRPlayerController.csOVRResetOrientation.csOVRRTOverlayConnector.csOVRSceneSampleController.csOVRScreenFade.csOVRWaitCursor.cs- No it wasn't added (everything was working okay still). But I added OVRManager to the scene (to camera) and submitted a build again. We just got the same "Reserved Interactions Test" warning in the review.
The weird thing is that, "Reserved Interactions" just work exactly described in the fail message, in our test device (S6 with up to date Oculus app). We cannot reproduce the failing state. - I think I will create a fresh new application with Unity and then build on top of that, incrementally adding features.
- I'm having exactly the same problem.. did you find a solution?
- I'm informed that the Oculus staff is working on this issue.
- Yeah of course, that would be really helpful!
how would you like me to send it to you? Attach to a message or send you a link to dropbox?
it's 30mb so wouldn't want to clog up your email server.. - This problem has been resolved by the Oculus staff. Great support, thanks a lot.
