Hi Meta Support Team! Thank you so much for getting back to me. 🙏
We know that receiving a response filled with copy-pasted generic troubleshooting steps - especially when it's an issue that’s already been widely reported and clearly tied to your latest update - is never ideal, so we want to acknowledge that we tried reading it anyway!
We understand this issue started after updating to the latest PTC version, and while we were hoping for insight or acknowledgment of the known bug, we were instead gifted a list of steps like:
- Restart the Headset
- Log out and back into the phone app
- Uninstall the app, restart the headset, reinstall the app
Truly cutting-edge techniques here! These steps are especially useful for addressing a repeatable, software-level problem introduced by a specific version update. We’re sure rebooting and reinstalling will magically rewrite code.
Now, because this issue began right after a new firmware update and has been echoed by others, we’d love for you to maybe also submit a bug report to your own team, just in case they’re still unaware of their own changes. But yes, I’ve already submitted one through the steps you listed - multiple times, in fact.
Oh! And suggesting to leave the PTC program as a workaround? Genius! Because nothing says “we value testers” quite like recommending they abandon the test as soon as something breaks. That’s how progress works!
To summarize:
- Issue? Still broken.
- Steps? Already tried them.
- Helpfulness? Hovering somewhere between “vague reassurance” and “good luck with that.”
- Confidence in resolution? We'll circle back after the next lunar eclipse.
...I’ll continue checking the forums for actual updates, and in the meantime, if there's a support script update that involves actually acknowledging confirmed bugs instead of treating them like user error, please feel free to reach back out.
Warm regards from your increasingly skeptical VR family,
BigSoulja