`LockedCameraCaptureManager` practically unusable since iOS 26

Somewhere since iOS 26, the LockedCameraCapture framework gets in an unpredictable state after opening the main app from the LockedCamera extension using LockedCameraCaptureSession.openApplication(for userActivity:).

(Feedback with sample code to reproduce: FB21966835)

Opening the extension from the lock screen again doesn’t open the extension but puts the lock screen in a state as if it has. Content updated from LockedCameraCaptureManager.shared.sessionContentUpdates comes in inconsistently, usually needs the app to be opened again or the extension to be opened.

This makes using this extension impossible for me as I use it to record video files that manually need to be imported when the app is launched (so not through PhotoKit).

Does anybody have a suggestion to circumvent this issue or how to get this fixed?

I’ve noticed the same issue on iOS 26. Sometimes the Lock Screen performs the zoom-out animation, but the extension doesn’t launch.

This bug has been haunting me since iOS 26 came out and there is little to no discussion anywhere. Thanks for posting this and I hope Apple really is aware and will resolve this quickly as the extension is a crucial feature of the app I'm developing.

I filed a bug report via Feedback Assistant back in Feb but haven't heard anything. I kindly ask everyone who is affected by this issue to also file a report (if you haven't done so yet) in the hopes that Apple would pay more attention.

`LockedCameraCaptureManager` practically unusable since iOS 26
 
 
Q