A few days ago, Meta's servers experienced a large area of downtime, including Facebook, Threads and Quest, and the Quest headset screen would pop up an "error" prompt, and the main system interface could not be called, and there was no way to launch any applications. In this case, Meta recently explained the reason for the failure of the Quest headset and said that it would enhance the resistance of the device.
Some believe that this is because the Quest headset needs to be constantly connected to Meta's servers. However, in general, even if you are offline and not connected to Meta's servers, the Quest headset can still use local functions normally. So, why do similar failures still occur?
According to the imagination of foreign players, this situation arises when either Meta's servers issue logout commands to all applications and devices, or the client security check deems the login token to be no longer secure, just like the user clicked "log out" in the headset settings.
In an article on X, Meta CTO Andrew Bosworth echoed the idea: "Yes, that's it. This is an unexpected result, and we are working to fix it. ”
In another tweet, Mark Rabkin, VP of Meta VR, further added that it would increase the resistance of the device. "Quest does work offline, but in this case [the server goes down] the login server error and returns an unexpected response to the headset, resulting in an invalid session," he explains. We will work to improve its adaptability to this super rare condition. ”
So the root cause of this error is the account protection mechanism provided by Meta. If a user's account is compromised, Meta will force all accounts to be logged out through the server. Of course, the premise is that the account is stolen, and this time the problem is that there is no problem with the user's account, but the server still sends a forced logout command to the networked user device.