Oculus platform error during user proof check timeout during fetching DSAT

[brenduchiha]

i recently started playing vr after 5 months and realised that i couldnt load into gorilla tag lobbies and couldnt get into vrchat and yeeps hide and seek at all instead it showed me the message "Oculus platform error during user proof check timeout during fetching DSAT if problem keeps occuring try restarting the headset or reinstalling the game". and when that didnt work i searched on youtube and found that the only way of fixing this is a factory reset. that worked for some time until like a week later i got the same problem. and now it just keeps happening even if i factory reset the headset 2 days later it'll just show up again and honestly im just tired of it can someone please help me.

[MetaNinjaTurtle]

Hey @brenduchiha 

Appreciate that you've went and tried a lot of possible fixes for this issue.

From researching your issue, it seems that some of our awesome community forum members have found a fix for it.

Here is the link to the community post -> Solved VR chat issue

If you need further help please don't hesitate to contact our support team on the forums or here!

Hope this helps! 🐢

[hazel.19090]

I've recently started playing VR again after a 5-month break and encountered a recurring issue with multiple games like Gorilla Tag, VRChat, and Yeeps Hide and Seek. Whenever I try to load into lobbies or launch these games, I get the error message: 'Oculus platform error during user proof check, timeout during fetching DSAT. If the problem keeps occurring, try restarting the headset or reinstalling the game.' I've tried the suggested fixes like restarting the headset and reinstalling the games, but they don't work. I found a YouTube video that recommended a factory reset, and while that temporarily fixes the issue, the error reappears after about a week. Now, even repeated factory resets only work for a few days before the error comes back. Can someone explain why this keeps happening and if there’s a more permanent fix to stop this error from reoccurring? Any advice or insights would be greatly appreciated, as I'm frustrated with constantly resetting the headset.