Closed jesperlundqvist closed 2 years ago
Thanks for the stack trace. These should be handled and addressable from the AppVoiceExperiences.events.onError event. We still log them out to the console. If the exception isn't being caught and passed to the onError event that's a bug. I'll take a look.
I have a fix for this prepped. It should be pushed in the next 24 hr o so.
This should now be fixed as of https://github.com/wit-ai/wit-unity/commit/c5304e1ed7cb86ca2a79bc7eb1ed9ad7db94e31b
If the device is not connected to the internet we get an Http error which is not handled. When running in the Unity editor or as a development build, this produces the stack trace as you can see below. However, when running a build without the development tag checked, the application crashes.
This can be reproduced in the Unity editor by turning off the internet adapter on your computer, which will give you the stack trace below after speaking into the microphone. The crash can be reproduced on Oculus Quest 2 by disabling WiFi in the settings and speaking a word into the microphone.
This is using the latest Oculus Voice SDK (version 37).