Forum Discussion

🚨 This forum is archived and read-only. To submit a forum post, please visit our new Developer Forum. 🚨
RADeSimone's avatar
RADeSimone
Honored Guest
3 years ago

Unable to verify developer account

2-factor authentication will not work for some reason. Used an authenticator app and was not verified. Tried giving my phone number but never received a code to input. Please help, thanks.

12 Replies

  • Sylfar's avatar
    Sylfar
    Honored Guest

    Having this exact same issue. Put in my phone number several times, never received a text message. Added 2FA through an Authenticator app, my settings show I have 2FA set up, but it's still not considered verified.

  • I have got 2 factor enabled on Meta account but Oculus verify page doesnt pick it up. If I press the setup buton it takes me straight to Meta page where it is enabled. 
    I have tried to raise a ticket but got brushed off and told to ask in the forum.
    If anyone has got this working can you please let us know.
    Thanks

  • Zemllia's avatar
    Zemllia
    Honored Guest

    Seems like i have same issue.

    Page shows next message when i'm pressing "submit" button:
    This Page Isn't Available Right Now
    This may be because of a technical error that we are working to get fixed.

    DevTools shows next error (i think this thats whats cousing everything to go wrong):
    wCGjnTvW8il.js?_nc_x=Ij3Wp8lg5Kz:61 ErrorUtils caught an error:

    Minified React error #31; visit https://reactjs.org/docs/error-decoder.html?invariant=31&args[]=object%20with%20keys%20%7B__html%7D for the full message or use the non-minified dev environment for full errors and additional helpful warnings. [Caught in: caught error in module y [from FRLAuthReauthenticatedPage.react] (base)]

    Subsequent non-fatal errors won't be logged; see https://fburl.com/debugjs.

     

  • I created a ticket #43044 (Oculus Developer Support) for this but they didn't get me support because it wasn't on their table. However, they gave me a link to this forum and I can see that it has to be an issue here.

    I tried three different cell-phone numbers but no confirmation codes has arrived. Also setup a Google Authenticator but it's probably not enough to be compliant.

    In general, I'm pretty tired of how difficult it is to create software for this platform.

  • Kudos to AlexUSAhome for the service https://receive-smss.com/sms/447868150810/ πŸ‘

    This method makes it 100% more unsafe but I just wanted to verify my account to continue with the game-development.

    It was extremely frustrating to not be able to update my Quest 2 with a new fresh build.

    -100 Kudos to the Oculus/Meta team for a completely broken sms-authentication-service!

  • I have the same issue. Really frustrating, because Oculus Support do not care about this problem...

    • dromni_gmbh's avatar
      dromni_gmbh
      Explorer

      HI everyone,

      I only want to share how it worked for me:
      I deleted the 2FA and Telefonnumber on the meta account page and under facebook and I try it again. This worked for me.
      Still frustrating to try it 100 ways until something worked...

  • AmaruqTheWolf 

    I am having the exact same problem. I created then deleted my 2FA. Didn't work. Then I linked my phone number and that didn't work. If you have fixed this, PLEASE reply and tell me how to fix it.

  • Same here.  I felt a bit violated the other day by sending my drivers licence but Meta forced me to do it so I can continue development.  Now, it wants more personal information so I'm once again stuck having to activate 2FA and give my phone number but I never receive the code.  I can still continue local development but this will need to be resolved soon.

  • I FOUND A SOLUTION!

    I contacted support and they said to put in credit card information and it worked.

    • Lyverbe's avatar
      Lyverbe
      Protege

      Yeah, well they say that you need to enter your credit card information *OR* your phone number.  I rather put my phone number than whatever that can steal money from me.  I don't see this as a solution, I see this as a workaround to a bug.