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!

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.

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.

I encountered the same issue. I tried to investigate different scenarios with various colleagues. If a user upgrades directly from an iPhone running iOS 16 or earlier to iOS 18, or uses the migration feature to move to iOS 18, the certificate does not appear in the Certificate Trust Settings (Full Trust for Root Certificates) list. However, the same certificate can be successfully installed on an iOS 18 device that hasn’t gone through migration or on a device that has upgraded from iOS 17 to iOS 18, where it appears normally in the Certificate Trust Settings list. We attempted many solutions and initially thought there might be an issue with our certificate. However, we then directly installed Apple's official Apple PKI webpage (https://www.apple.com/certificateauthority/) and downloaded a certificate for testing. We found that devices with these issues also failed to display the certificate in the list for enabling it. Currently, the only workaround is to reset the entire phone and not use the migration feature or upgrade from iOS 16 or earlier to iOS 18. Only then will the certificate display correctly in the Full Trust list. I'm not sure if this bug will be fixed.