IOS 26.1 isSourceTypeAvailable: UIImagePickerControlSourceTypeCamera method keeps returning true when the camera is unavailable

We have encountered the same issue: in iOS 26.1 Beta 1, the behavior was normal, but after upgrading to iOS 26.1 Beta 2, regardless of whether the device has a camera, [UIImagePickerController isSourceTypeAvailable:UIImagePickerControllerSourceTypeCamera] always returns YES (true). We hope this can be fixed in the next version.

Have either of you filed a bug on this? If so, what's the bug number?

__
Kevin Elliott
DTS Engineer, CoreOS/Hardware

iOS 26.1, the isSourceTypeAvailable: UIImagePickerControlSourceTypeCamera method keeps returning true when the camera is unavailable.

Just to be sure I'm clear on the issue, the camera itself is disabled, but your app ends up showing the camera UI (because we said the camera was there)? Is it coming up with a black screen, or does something else happen?

Do you have any good solution? Or can we just wait for the bug to be fixed?

You might try checking AVCaptureDevice.authorizationStatus(for:), as it's possible that the lower-level API will give you a different answer, particularly if you're getting a black screen from UIImagePicker.

If that doesn't work, then I think your only option is to wait for a fix.

__
Kevin Elliott
DTS Engineer, CoreOS/Hardware

We tried testing this in two ways. The first was by disabling the Camera App in Settings App → Screen Time → Content & Privacy Restrictions → Allowed Apps & Features. We used the API [UIImagePickerController isSourceTypeAvailable:UIImagePickerControllerSourceTypeCamera] to return YES and checked AVAuthorizationStatus was AVAuthorizationStatusAuthorized. The other was by setting the profile mobile config setting allowCamera to false. The test results were still the same: always return YES. I think it's an Apple iOS 26.1 beta2 beta3 bug and hope it can be fixed as soon as possible. Thank you.

bug number: FB20744645 Please help reflect and correct it as soon as possible, thank you for your assistance @DTS Engineer

OS 26.1 RC has been released, but the API UIImagePickerController.isSourceTypeAvailable(.camera) still always returns true without any fix. Are there any alternative workarounds? This issue allows third-party apps to access the camera even when it is restricted, resulting in a severe security vulnerability. I have submitted bug reports with the following IDs: FB20863542 and FB20660883 I urge the team to fix this before the official release or provide an alternative API to reliably check camera availability.

OS 26.1 RC has been released, but the API UIImagePickerController.isSourceTypeAvailable(.camera) still always returns true without any fix. Are there any alternative workarounds?

No, I don't think so.

This issue allows third-party apps to access the camera even when it is restricted, resulting in a severe security vulnerability. I have submitted bug reports with the following IDs: FB20863542 and FB20660883 I urge the team to fix this before the official release or provide an alternative API to reliably check camera availability.

I can't comment on our release schedule or plans, however, I can tell you that this issue is being taken very seriously and that everyone involved understands how serious this issue is.

__
Kevin Elliott
DTS Engineer, CoreOS/Hardware

this bug has been fixed in the official ISO 26.1 release. Thank you for resolving it in the new version! I’m not sure if my report prompted the fix, but I truly appreciate it nonetheless. That said, I hope in the future the bug-reporting website can provide real-time acknowledgment—something like “received, under review”—instead of one-way submission with zero feedback. Thank you!

this bug has been fixed in the official ISO 26.1 release. Thank you for resolving it in the new version!

You're very welcome. I'm sorry I couldn't be more specific in my earlier post, but when I posted my earlier email the fix was already making it's way into the final build.

I’m not sure if my report prompted the fix, but I truly appreciate it nonetheless.

Yes, your bug played a significant role in making sure this got fixed.

That said, I hope in the future the bug-reporting website can provide real-time acknowledgment—something like “received, under review”—instead of one-way submission with zero feedback. Thank you

That's feedback we hear a lot. I'd love to see it as well, but the volume of bugs and our own secrecy requirements make it a difficult issue to address.

__
Kevin Elliott
DTS Engineer, CoreOS/Hardware