Meta Quest Pro Eye & Face Tracking Suddenly Stopped Working — Same Issue on Two Headsets

I've been using the Meta Quest Pro for quite some time, and recently the eye and face tracking on my original headset suddenly stopped functioning properly.

At first, I suspected that the issue might have been caused by hardware damage, possibly from moisture or sweat. Because of that, I purchased a replacement Quest Pro headset that is in like-new condition. However, I'm experiencing the exact same issue on the replacement headset, which makes me wonder if this could be related to a software, firmware, or account-level issue rather than a hardware failure.

Here is what I'm experiencing:

• Eye Tracking Calibration: The calibration process completes successfully without any errors. During the calibration/tracking test, the ball follows my eye movements accurately, so the headset appears to be detecting my eyes correctly.
• Standalone Apps: However, once I enter standalone applications such as Meta Horizon Worlds, eye tracking becomes extremely inaccurate or barely functions at all.
• Face Tracking: Facial/face tracking does not appear to register at all.
• Settings: Both Eye Tracking and Natural Facial Expressions are enabled in the headset settings.
• Two Separate Headsets: Most importantly, the exact same behavior occurs on both my original Quest Pro and my replacement Quest Pro.

Because the tracking calibration works correctly but the features fail or perform extremely poorly once I'm actually using standalone applications, I'm wondering if something is preventing the tracking data from being properly utilized after calibration.

I've already considered the possibility of hardware failure, but experiencing the identical problem on two separate Quest Pro headsets makes that seem much less likely.

Has anyone else experienced this recently? Could this be a Meta Quest firmware/software bug, an issue with Horizon Worlds, an account setting, or something else that could affect eye and facial tracking?

I'd really appreciate any troubleshooting suggestions or information from anyone who has experienced the same problem. If there are specific settings, firmware versions, developer options, factory-reset procedures, or other fixes I should try, I'm willing to give them a shot.

Thanks in advance!