Wherever possible, we'll try to explain the problem on the message we display.
Usually, if you receive an error message while playing FitXR, it should come with a short description of what the problem is - along with our support email for further help. This will vary though, as it depends on whether it's an error in our app, or something from one of the services that helps run it (where we can't control the wording).
Below, we've listed some of the numbered errors you might get, along with any known workarounds. If you ever need more support please don't hesitate to reach out to us on support@fitxr.com.
Numbered errors
1000.408.0-5
NB: The two numbers at the end may vary
This is a time out error which means the server is having trouble establishing a connection with your network, which stops the class from starting. This is often caused by a slow or disrupted internet connection. Please try the following workarounds if you're experiencing this error:
Check your internet speed, if it looks good then disconnect and re-connect your headset to your WiFi
Try connecting your headset to your mobile hotspot and then if you're able to start a class, connect back to your WiFI
1100.408.0-5
NB: The two numbers at the end may vary
This is a caching error, caused by the app not fully having downloaded a class - or where the information downloaded is corrupt. If you receive this error during a workout, please try the following:
Clear your cache. You can do this from the FItXR home menu by going to Settings and then selecting 'Clear Cache'.
Still need help?
If the solutions above don't work, or you receive a different error code then please get in touch with us right away so we can investigate this further. You can do this by sending an email to support@fitxr.com or clicking the 'Support' button in the bottom right hand corner of this page. If possible, please also let us know the following information:
The exact error code you're receiving
At what stage you're experiencing the error message
Your Meta OS version number (this can be checked by going to Settings > About from the Meta home menu)
Anything you've tried to resolve the issue yourself.