iOS 16+ crash about natdevice

[V0odo0]

No, but we have another plugin that is used for audio recording. Will look into it tomorrow.

[olokobayusuf]

This seems to be happening because another app is in control of the microphone. When the crash happens, do you have a call or another app recording the mic?

[olokobayusuf]

Looking online, it seems that a fair number of developers have been facing a similar issue with iOS 16.

[olokobayusuf]

@V0odo0 Sounds good.

[V0odo0]

Tested with disabled Speech To Text plugin. Same crash.

No crash on iPhone 11 with iOS 16.2.

Our app with old version of NatDevice is working fine. Indeed there is something related to NatDevice. Any thoughts?

[olokobayusuf]

Try out the following and let me know the result:

1. In Player Settings, make sure that Prepare iOS for Recording is enabled.
2. In code, before doing new MediaDeviceQuery, add the following:

MediaDeviceQuery.ConfiguresAudioSession = false;

[olokobayusuf]

@V0odo0 I got around to testing this on iOS 16.2, wasn't able to repro. I mentioned this earlier:

This seems to be happening because another app is in control of the microphone. When the crash happens, do you have a call or another app recording the mic?

Can you confirm that there isn't another app running that is already using the microphone?

[V0odo0]

Try out the following and let me know the result:

1. In Player Settings, make sure that Prepare iOS for Recording is enabled.
2. In code, before doing new MediaDeviceQuery, add the following:

MediaDeviceQuery.ConfiguresAudioSession = false;

Didn't help unfortunately.

@V0odo0 I got around to testing this on iOS 16.2, wasn't able to repro. I mentioned this earlier:

This seems to be happening because another app is in control of the microphone. When the crash happens, do you have a call or another app recording the mic?

Can you confirm that there isn't another app running that is already using the microphone?

Yes. We disabled microphone usage for all apps in iOS settings. Our app is not in the list since it is not using microphone.

We experience this crash on at least two devices (iPhone 14 with iOS 16.2). No crash on iPhone 11 with iOS 16.2.

[V0odo0]

The issue was resolved after iOS 16.3 fresh update. Looks like this bug was specific for iPhones 14 with iOS 16.2.

[olokobayusuf]

That sounds good. Thanks for letting me know.

[V0odo0]

That sounds good. Thanks for letting me know.

Whoops. Actually it was the first succesfull application launch. But second time we got a crash again. iPhone 13 as well.

What I'm noticed that the crash occurs randomly (but most of the time) when we querying video devices. iOS just killing the application. Maybe it happens because of high CPU usage spike?

[olokobayusuf]

What I'm noticed that the crash occurs randomly (but most of the time) when we querying video devices. iOS just killing the application. Maybe it happens because of high CPU usage spike?

This shouldn't be the case. When the app crashes, can you share the logs from Xcode? iOS (along with macOS) are pretty diligent about collecting call stacks/stack traces when a crash occurs, so Xcode should always be able to catch the crash so you can inspect it. Share away!

[V0odo0]

What I'm noticed that the crash occurs randomly (but most of the time) when we querying video devices. iOS just killing the application. Maybe it happens because of high CPU usage spike?

This shouldn't be the case. When the app crashes, can you share the logs from Xcode? iOS (along with macOS) are pretty diligent about collecting call stacks/stack traces when a crash occurs, so Xcode should always be able to catch the crash so you can inspect it. Share away!

XCode log is in the first post.

Here is the part of the code where we querying for devices:
var filter = MediaDeviceCriteria.CameraDevice;
var query = new MediaDeviceQuery(filter);
foreach (var q in query)
{
var device = q as CameraDevice;
if (device != null)
all.Add(new NatDeviceVideoStream.Info(device));
}

[olokobayusuf]

If the error remains the exact same, then it's safe to assume that this is still an iOS issue. So I'll close this issue.