Skip to main content
Strategos
Participant
March 5, 2020

Cannot Pair Quest with Test Account

I've setup a test account, factory reset my Quest, logged into the Oculus app on my phone and tried to pair.

If I try to pair with existing HMD
"Headset Identity cannot be verified at this time. please try again" 

If I attempt to "Pair with new headset"  
It asks for the 5 digit pin but nothing shows up in the HMD.

It all worked fine with my regular account prior to this.

Any solutions for this issues much appreciated as I'm on a deadline!

    7 replies

    StrategosAuthor
    Participant
    March 5, 2020
    Note: I've restarted everything multiple times in different sequences, reinstalled the Oculus App. Tried the process with and without the USB cable plugged in.   Restarted my phones bluetooth. 
    StrategosAuthor
    Participant
    March 5, 2020
    Worryingly I can find another thread with the same issue with no resolution...
    https://forums.oculusvr.com/developer/discussion/comment/713282#Comment_713282
    StrategosAuthor
    Participant
    March 5, 2020
    I've seen the 5 digit pin and notice that it is always the same, so can input that when trying to the Pair With a new headset option.

    But it then simply says "Cannot connect to headset" 

    The process works fine if I use my normal Oculus account. 
    StrategosAuthor
    Participant
    March 6, 2020
    I have purchased a second android phone which just has the test account on it. Still will not connect . 

    I realise i'm just shouting into the void here.
    StrategosAuthor
    Participant
    March 6, 2020
    Finally for anyone else that encounters this issue. 

    It was a problem with the Test Account itself. We haven't found exactly what, a permissions problem potentially. But if you are suffering from this problem that's the first place to look. I  used a work colleagues test account and that successfully paired.
      LionZuck
      New Participant
      August 10, 2022

      **Deleted**

      Strongbearceo
      Participant
      March 10, 2024

      It's 2024 and still a problem

        Terms & ConditionsAccessibility statement