After creating multiple test accounts and using these to test our games for over a year, we are suddenly facing a strange process that we cannot figure out how to solve.
When you as a developer create test accounts, you can set the prefix, password and pin. Before you could always sign into an account by inputting a code in meta.com/device
The issue now is that when you try to add another profile, a test account in this case, it send a link the user needs to confirm.
How are we supposed to accept a link sent to a test email?
Our company is blocked by the inability to add test user accounts to our devices. When I try, it says that a confirmation code was sent (to the test account's nonexistent email address), and I have 15 minutes to enter it.
There is no other option to verify the account via password or anything else, either in the headset, in the app, or on the auth website.
Especially frustrating is the fact that the instructions on the website to setup a test user say to "Enter the 8 digit code you got from your headset in step 13 above" but there is no step 13! The steps in the previous section end at 12!
I ran into the same roadblock. I created ~10 test accounts for the same number of Quest 2 devices which we want to use for teaching at our university. All the setup work required to get this up and running is nullified by this painful problem.
This has set back the teaching schedule significantly as students are unable to work on the headsets as we intended.
I'd be super interested in a fix. Or maybe I am doing something wrong. Or heck, even a workaround of any sort seems like a viable solution at this point.
After trying to work with three different tech support techs who were all laughably incompetent and didn't even know what test accounts were, I gave up and just made a "real" account with a burner email address. And that has worked out just fine. Totally totally stupid to have this service that's completely broken. Obviously the left hand doesn't know what the right hand is doing, and someone set up the email authentication without realizing that it would break test accounts.
@uncle_hunty I was fearing such an outcome. I'm still in back-and-forth with support for a good few days now and there's no end in sight. If nothing works I'll have to undo all the work here and create non-org accounts, or have users use their own accounts. This is very cumbersome as a headset might be used by different students throughout a week. Very frustrating.
We just got rid of the issue.. I think, Now its mandatory to add test user using MQDH. Add test user here. Then we will get 8 digit code as usual before. Try it..
