We're seeing the same thing in our app, and can reproduce it reliably: Press the Lock Screen control. The camera extension opens normally. Take a photo, then call LockedCameraCaptureSession.openApplication(for:) to open the main app. Lock the phone. Press the control again. There's a slight animation, but the camera never appears. The phone looks hung until you swipe or lock again. From our own logging in the extension: The extension process is suspended almost immediately after openApplication(for:) is called, before the call returns. Its scene is never disconnected. We kept the process alive with ProcessInfo.performExpiringActivity and waited up to 25 seconds for the scene to go away; it never did. Calling exit(0) in the extension after the hand-off didn't help either. The next press still showed nothing. This matches the report in FB21966835, which describes the Lock Screen camera being left in an unpredictable state after handing off to the app. It looks like system state rather than anything inside the extension. It would be great to know whether this is a known issue, or whether there's a supported way to hand off to the app without breaking next launch.