Welcome to the Oculus Developer Forums!

Your participation on the forum is subject to the Oculus Code of Conduct.

In general, please be respectful and kind. If you violate the Oculus Code of Conduct, your access to the developer forums may be revoked at the discretion of Oculus staff.

Functional Tests Review: What does this feedback message mean?

ProfessorTroyProfessorTroy Posts: 80 Poster of the Week
Hello!

The message I got back from my latest submission says:
"Your application exits immediately on quit command or device removal. "

Are they saying it shouldn't exit immediately, or are they saying it didn't?
@cybereality  - shed a little light on this one because I suspect they mean it didn't exit properly when it should have.

Answers

  • Swamp7hingSwamp7hing Posts: 37 Oculus Start Member
    edited July 2016
    I also received this testing notification and would like some additional clarification. Looping in @lisabrewster and @cybereality!
  • dlightvrdlightvr Posts: 1
    NerveGear
    I also had this message, do you have any idea how should I fix?
  • FulbyFulby Posts: 184
    Art3mis
    edited July 2016
    I think some of these rejection reasons have canned text which is added due to the tester ticking a box, so the reason doesn't always exactly match the cause of the problem. One rejection message I received was

    "During testing we experienced progression blockers, crash events that led to data loss such as saved games status and downloaded assets. The Quickstart Menu covers the main menu making it impossible to access options, etc."

    The second sentence is the useful one and refers to a menu in my game. I don't believe there was data loss and crashes, it was just that this was the most appropriate canned response available (being a progression blocker).

    Not sure if this will help but when pressing the back button at the 'top level' of the app/menu, there's supposed to be a confirmation dialog when exiting the app. Maybe your apps are exiting immediately without the confirmation?

    https://developer.oculus.com/documentation/mobilesdk/latest/concepts/mobile-umenu-intro/



  • ProfessorTroyProfessorTroy Posts: 80 Poster of the Week
    Interesting suggestion that the exit commands within the game also need a confirmation.
    I know my back button functionality works and shows it, but I also have an in-game option to exit as well that doesn't show confirmation if you select it.
  • Swamp7hingSwamp7hing Posts: 37 Oculus Start Member
    @fulby I get the confirmation exit to Oculus Home dialog with the Back button short press and the long-press takes me to the Oculus Menu in which you can also quit back to Home. It is my impression that these functions are controlled by the OVR SDK and therefore are out of my control and would not affect the test. Not sure what to do here.
  • FulbyFulby Posts: 184
    Art3mis
    @Swamp7hing do you have an in-game button for exiting the app? If so, does it show a confirmation dialog (either your own or Oculus' one)?
  • Swamp7hingSwamp7hing Posts: 37 Oculus Start Member
    Nope, I simply have the Oculus back button running my game quit command as per the OVR SDK. I had an exit button in the menu of my game but removed it - at the time, the exit button in the menu did not show the confirmation. Could this have been the problem being flagged by the test?
  • FulbyFulby Posts: 184
    Art3mis
    Maybe, I'm just guessing. I'd resubmit the game as it is now and see if it passes that test.
  • motorsepmotorsep Posts: 1,468 Oculus Start Member
    Hmm.. I think when you remove phone from Gear VR app should be closed. That's what happens to all apps afaik. Doesn't make sense to keep it running in the background and taking up resources.

    Back button short press should bring either custom confirmation or stock Oculus confirmation. Long press should go into universal menu.
  • Swamp7hingSwamp7hing Posts: 37 Oculus Start Member
    @Fulby sweet, just need to wait for that "Under Review" flag to swap over so I can submit a new binary. Cheers! Fingers crossed.

    @motorsep Yep, that's the behavior here. The app closes entirely when the phone is removed, pauses when the HMD is removed, and performs the Back button long/short press functions as you've described. Hopefully once I'm able to submit a new binary the test flags the Functional portion as passed.
  • ProfessorTroyProfessorTroy Posts: 80 Poster of the Week
    Make sure you're also handling the volume buttons properly as well @Swamp7hing
    A bunch of us missed that one after getting these other ones sorted out.
  • Swamp7hingSwamp7hing Posts: 37 Oculus Start Member
    Yup, the Volume UI is operating as expected and triggering with the Gear Volume Rocker - thank you for the reminder! Out of curiosity, how long have you been waiting (or did you wait) for the app status to change from Under Review?
  • ProfessorTroyProfessorTroy Posts: 80 Poster of the Week
    I entered two support tickets, waited a week and a half, then went through a back channel and it got updated so I could submit a new build. However, before I do so, I'm making sure I catch everything this time and my app behaves like other apps.
  • Swamp7hingSwamp7hing Posts: 37 Oculus Start Member
    edited July 2016
    Thanks @ProfessorTroy! The status swapped back today and I submitted a new build for review. Without the older devices to test the stable framerate I'm shooting in the dark, but I went fully Mobile with my shaders, minimized my materials, and did a few graphical optimizations so I'm hoping it will run on them.

    If anyone has an S6/Note 5 and would be willing to pop it in for a stability check let me know ASAP!
  • FiresVRFiresVR Posts: 2
    NerveGear
     Hello @Swamp7hing  and @ProfessorTroy , have you resolve this question? Our app has same problem with "Your application exits immediately on quit command or device removal. " 
  • ProfessorTroyProfessorTroy Posts: 80 Poster of the Week
    Not yet. I however, haven't re-submitted yet either.  I have a few more things I want to button up before wasting their review teams time.

    I have done the following two things however with the expectation that I should have things fixed up.

    1. Any exit button from the game prompts the standard back button menu about leaving to the main home.
    2. I have added listeners to things like HMD removal and such so the game exits properly. Look at the events the OVRManager provides and make sure your application pauses and quits appropriately.


  • FiresVRFiresVR Posts: 2
    NerveGear
    Not yet. I however, haven't re-submitted yet either.  I have a few more things I want to button up before wasting their review teams time.

    I have done the following two things however with the expectation that I should have things fixed up.

    1. Any exit button from the game prompts the standard back button menu about leaving to the main home.
    2. I have added listeners to things like HMD removal and such so the game exits properly. Look at the events the OVRManager provides and make sure your application pauses and quits appropriately.


     Thank you, it seems we are going to do same things and submit a new version later!
Sign In or Register to comment.