⚠️ Important: As of Meta Quest firmware version v74 and above, it is no longer possible to enroll devices using Meta Test User accounts. Meta devices must now be enrolled using Meta Horizon managed services. The information below is intended for reference only and applies to some legacy devices.
In the past, it was possible to enroll Meta Quest devices at scale using Meta test user accounts. Test user accounts were previously an alternative to real consumer Meta accounts. This approach was widely adopted due to its simplicity and scalability when setting up large fleets of headsets. While this method is now deprecated for future devices (which are enrolled through Meta Horizon managed services and use managed Meta accounts), understanding how it worked can be helpful for those managing older deployments or troubleshooting legacy devices.
(Legacy) Benefits of using test user accounts
✅ Easy to generate: Test users can be created in bulk via developer.oculus.com.
✅ No authentication hurdles: No 2FA, credit card, or email confirmation required.
✅ Developer-enabled: Test user accounts are automatically in developer mode (which was previously a requirement for enrollment)
✅ Possible to create many: No documented upper limit on the number of test users that could be generated.
(Legacy) Limitations of using test user accounts
❌ No access to Meta Store or social features: Test users cannot download store content or access Horizon social experiences.
❌ Required business verification: Your Meta Developer account had to be verified to generate test users.
❌ Now deprecated: As of firmware v74+, it is no longer possible to use test user accounts to provision devices through the ManageXR Device Setup Tool. You must provision devices using Meta Horizon managed services.
FAQs and troubleshooting
Q: Will my devices that were set up using test users continue to work?
Q: Will my devices that were set up using test users continue to work?
Yes. There has been no indication that existing test users will be eliminated. We have seen occasional cases of test users disappearing (see FAQ below), but these can usually be resolved by following the instructions Meta provides.
Q: What’s the maximum number of test users I can generate?
Q: What’s the maximum number of test users I can generate?
There is no officially documented limit, but we’ve observed performance degradation when generating more than 1,400 test users under a single developer account. The most we’ve seen successfully created is around 1,600. To avoid issues, consider splitting the load across multiple developer-enabled accounts.
Q: Why did my test user accounts disappear after device pairing?
Q: Why did my test user accounts disappear after device pairing?
This is a known issue. When pairing a device, Meta may prompt the user in-headset to share additional data. If you choose "Don’t Share", the test user account is deactivated and removed from your developer.oculus.com dashboard.
How to fix it:
Sign in with the affected test user account at this link: auth.meta.com
Approve the prompt to share additional data.
It will look something like this:Reboot your device. It may appear briefly locked out—this will resolve after around 1 minute.
Refresh the test user list on developer.oculus.com. The account should reappear.
Q: Can I still use test users for development or testing?
Q: Can I still use test users for development or testing?
Test users may still be useful for limited local development, but they cannot be used to provision Meta Quest devices on firmware v74 and above. To enroll new devices use Meta Horizon managed services.
Need more help?
Talk to a member of our team using the chat bubble (in the bottom right of your screen), or reach out to support@managexr.com