Error while starting Microphone on Quest Pro while streaming to Horizon Managed Services
Hello everyone,
We're running into an issue with one of our apps that we developed and rolled out to Quest Pro devices.
This app is a training for medical personnel and uses the microphone to speak to virtual characters.
The app works fine on most Quest devices.
However, and error occurs when our app tries to record audio in specific circumstances.
One of our clients uses the app on Meta Quest Pro headsets, which are being managed via Horizon Managed Services.
When a student uses the app they sometimes get support from an examiner who uses the casting functionality in Horizon Managed Services to help the student.
When our app is running on the Meta Quest Pro headset, and the examiner starts streaming the headset to the browser, an error occurs in the app.
The method Microphone.Start() is called within Unity to start recording when the student holds down one of the triggers on the Quest controllers.
When the student does this while using the app on a Meta Quest Pro headset while it's casting to a browser via Horizon Managed Services, it throws the following error:
"Starting microphone failed: "An error occured that wasn't supposed to. Contact support. " (33)"
The attached image is a photo taken by an examiner, it shows the Horizon Managed Service casting page.
On the casting page you can see the view of the student, which shows an error message.
This error message is not the above error message, but a custom exception message we show our users while the app transmits the error details to our server.
We tried to reproduce the error using Meta Quest devices we have available in our office.
We have a Meta Quest 3S headset which also uses Horizon Managed Services. We installed and started the app, and started casting to the browser, but the error does not occur.
The error only seems to occur on Meta Quest Pro headsets while these are casting to Horizon Managed Services.
Since the error does not occur on Meta Quest 3S headsets, this seems to be some kind of issue within the operating system within the Meta Quest Pro?
Can you help with debugging this issue?