You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We recently received a crash report on our app and our reporting service identified the handleRouteChange method in OTDefaultAudioDevice as the most likely cause. We don't have our own implementation of this file so this is the built-in file from OpenTok. Unfortunately it doesn't give the line of code but it gives this crash log:
NSRangeException (crashed)
Application threw exception NSRangeException: *** -[__NSArray0 objectAtIndex:]: index 0 beyond bounds for empty array
From looking at the user journey data, the user started connecting to a session and then received a phone call whilst this was happening. I believe this meant the audio process was being taken up by the phone call and OpenTok was unable to setup audio as there was no device available. It's a fairly edge case scenario but a user has experienced it so it's worth investigating.
Hello
We recently received a crash report on our app and our reporting service identified the handleRouteChange method in OTDefaultAudioDevice as the most likely cause. We don't have our own implementation of this file so this is the built-in file from OpenTok. Unfortunately it doesn't give the line of code but it gives this crash log:
NSRangeException (crashed)
Application threw exception NSRangeException: *** -[__NSArray0 objectAtIndex:]: index 0 beyond bounds for empty array
From looking at the user journey data, the user started connecting to a session and then received a phone call whilst this was happening. I believe this meant the audio process was being taken up by the phone call and OpenTok was unable to setup audio as there was no device available. It's a fairly edge case scenario but a user has experienced it so it's worth investigating.
Device: iPhone 13 Pro, iOS 17.6.1
SDK version: 2.72.2
Session ID: 1_MX40NzkwNjc3MX5-MTcyNDUxMDk3MTg0M35ob1QrTTB0clZUWk8vdEZXbVcrYlRsWjl-fn4
The text was updated successfully, but these errors were encountered: