Forum Discussion

🚨 This forum is archived and read-only. To submit a forum post, please visit our new Developer Forum. 🚨
Jazui's avatar
Jazui
Honored Guest
11 months ago

Quest Calls Not Working Since v67 Update

I have been experiencing a persistent issue with Quest calls ever since the v67 update. Prior to this update, I was able to join Quest calls without any problems. However, after the update, the following issues started occurring:

1. Initially, I would get kicked out of calls randomly.

2. A few days later, I was no longer able to join Quest calls at all.

 

Although I still receive notifications and other features work, every time I try to load into a call, it either:

- Kicks me out immediately.

- Displays an error message saying, “An error occurred. Please try again in a little while.

 

Steps Taken to Resolve:

I’ve tried every troubleshooting method suggested by Support, including:

- Resetting my headset.

- Performing a factory reset.

- Changing WiFi routers.

- Checking for WiFi-related issues.

- Using a mobile hotspot with a VPN.

 

Unfortunately, none of these solutions have resolved the issue.

So,

After following all troubleshooting steps, Support informed me that my country/region might not be supported. However, I have verified this claim to be false, as a friend in the same country/region can use Quest calls on his headset without any issues.

 

Additionally, I’ve previously resorted to using Meta calls on my phone as a workaround, but that feature seems to no longer exist.

 

This issue has persisted since the v67 update, and it has made Quest calls entirely unusable for me. Given that this problem started specifically with the v67 update and has not occurred in previous versions, I strongly believe it is related to the changes made in that update.

 

I am reaching out to bring this issue directly to the developers attention. Please investigate this matter, as it has disrupted my ability to use a core feature of my Quest headset.

No RepliesBe the first to reply