调用AVCapturePhotoOutput的capturePhoto方法为何崩溃？附无活跃视频连接报错

Hey there! Let’s dig into this AVFoundation crash you’ve been wrestling with for days—nothing’s more frustrating than a bug that only pops up after specific user actions like switching pages or flipping the camera. Let’s break down what’s happening and how to fix it.

First, What’s Causing the Error? #

This error means when you call capturePhotoWithSettings:delegate:, your AVCapturePhotoOutput doesn’t have an active, enabled video connection to work with. Most often, this happens because:

• Your camera session’s configuration gets broken during page transitions or camera flips (like not properly resetting inputs/outputs)
• You’re reusing a single AVCapturePhotoSettings instance across different camera states (front/back camera) which may not support the same settings
• You’re trying to take a photo before the camera session finishes reconfiguring after a flip or page switch

Targeted Fixes Based on Your Code Clues #

Since you’ve narrowed it down to code related to AVCapturePhotoSettings, here are the most likely fixes to test:

1. Never Reuse AVCapturePhotoSettings Instances

Front and back cameras support different pixel formats, resolutions, and features. Reusing a settings object created for one camera with the other can break the connection. Always create a fresh instance right before taking a photo:

// ✅ Do this every time you're ready to take a photo
AVCapturePhotoSettings *photoSettings = [AVCapturePhotoSettings photoSettings];

// Optional: Match settings to the current camera's capabilities
NSArray *supportedFormats = self.photoOutput.availablePhotoPixelFormatTypes;
if ([supportedFormats containsObject:@(kCVPixelFormatType_32BGRA)]) {
    photoSettings.preferredPhotoPixelFormat = kCVPixelFormatType_32BGRA;
}

2. Validate the Connection Before Taking a Photo

Add a quick check to ensure the photo output has an active connection before calling capturePhotoWithSettings:delegate:. This prevents the crash if the session is still reconfiguring:

- (void)triggerPhotoCapture {
    AVCaptureConnection *activeConnection = [self.photoOutput connectionWithMediaType:AVMediaTypeVideo];
    
    // Check if the connection exists and is active
    if (activeConnection && activeConnection.isActive) {
        AVCapturePhotoSettings *settings = [AVCapturePhotoSettings photoSettings];
        [self.photoOutput capturePhotoWithSettings:settings delegate:self];
    } else {
        // Reconfigure the camera session if the connection is broken
        [self rebuildCameraSession];
    }
}

3. Fix Camera Flip/Page Transition Logic

When flipping cameras or navigating away from the camera page, make sure you’re managing the session correctly:

• Page transitions: In viewWillDisappear, pause the session instead of destroying it entirely. If you do destroy it, ensure you fully reinitialize all session components (inputs, outputs, connections) when returning to the page.
• Camera flips: Follow this safe workflow:
  1. Stop the session with [self.cameraSession stopRunning]
  2. Remove the old camera input from the session
  3. Add the new front/back camera input
  4. Restart the session
  5. Wait for the AVCaptureSessionDidStartRunningNotification before allowing photo capture (don’t trigger capture immediately after restarting)

4. Ensure Thread Safety for AVFoundation Operations

All AVFoundation session modifications and capture calls should happen on a dedicated serial queue (not the main thread unless necessary). This prevents race conditions that can break connections:

// Create a serial queue for camera operations
dispatch_queue_t cameraQueue = dispatch_queue_create("com.yourapp.cameraQueue", DISPATCH_QUEUE_SERIAL);

// Use it for session changes and capture calls
dispatch_async(cameraQueue, ^{
    [self.cameraSession beginConfiguration];
    // Add/remove inputs/outputs here
    [self.cameraSession commitConfiguration];
    [self.cameraSession startRunning];
});

Final Checks #

If you’re still hitting the crash, double-check:

• Are you accidentally setting camera session or output objects to nil during page transitions, leading to dangling references when you return?
• Are you handling permission changes correctly? If the user revokes camera permission mid-session, it can break connections too.

内容的提问来源于stack exchange，提问作者TheRedCamaro3.0