iOS应用KVO随机崩溃求助：observeValueForKeyPath相关问题

Let's break down your issue and walk through actionable fixes to resolve these persistent crashes.

Key Observations from Your Crash Log & Code #

Your crashes originate in the temperatureAndTintValuesForDeviceWhiteBalanceGains: method, triggered by a KVO callback on videoDeviceInput.device.deviceWhiteBalanceGains. A few critical points stand out:

• The crash fires on the main queue (evident from the dispatch main queue trace)
• Reinstalling fixes the issue temporarily, pointing to state-related corruption or leftover observer/cache issues
• You add observers in viewWillAppear and remove them in viewDidDisappear, but this isn't always sufficient for full lifecycle safety

Likely Root Causes #

1. Incomplete Observer Cleanup: viewDidDisappear doesn't run in all scenarios (e.g., memory warnings that deallocate your ViewController without proper dismissal). If your ViewController is destroyed but observers aren't removed, KVO callbacks will fire on a deallocated object, leading to crashes.
2. Invalid Device/Parameter Access: When the KVO callback triggers, videoDeviceInput.device might already be nil/deallocated, or the deviceWhiteBalanceGains value could fall outside the valid range expected by the AVFoundation method.
3. Thread Safety Violations: AVFoundation operations (especially those involving AVCaptureDevice) should run on the capture session's dedicated serial queue, not the main queue. Your current callback executes on the main queue, which can cause race conditions.
4. Duplicate Observer Registration: If viewWillAppear is called multiple times (e.g., navigating back to the ViewController), you'll add duplicate observers. This leads to redundant callbacks and potential crashes when removing observers later.

Step-by-Step Fixes #

1. Add Observer Cleanup in dealloc (Critical) #

Add a dealloc method to guarantee observers are removed when the ViewController is destroyed, even if viewDidDisappear doesn't execute:

- (void)dealloc {
    [self removeObservers];
}

2. Guard Against Invalid Objects/Parameters in KVO Callback #

Update your observeValueForKeyPath:ofObject:change:context: method to validate inputs before calling the problematic AVFoundation method, and use the capture session's queue for safe execution:

- (void)observeValueForKeyPath:(NSString *)keyPath ofObject:(id)object change:(NSDictionary<NSKeyValueChangeKey,id> *)change context:(void *)context {
    // Only handle our custom KVO contexts
    if (context == DeviceWhiteBalanceGainsContext) {
        AVCaptureDevice *device = self.videoDeviceInput.device;
        // Guard against nil or incompatible device
        if (!device || ![device isKindOfClass:[AVCaptureFigVideoDevice class]]) {
            return;
        }
        
        AVCaptureWhiteBalanceGains gains = device.deviceWhiteBalanceGains;
        // Validate gains are within the device's supported range
        if (gains.rGain < device.minWhiteBalanceGain || gains.rGain > device.maxWhiteBalanceGain ||
            gains.gGain < device.minWhiteBalanceGain || gains.gGain > device.maxWhiteBalanceGain ||
            gains.bGain < device.minWhiteBalanceGain || gains.bGain > device.maxWhiteBalanceGain) {
            return;
        }
        
        // Execute AVFoundation operation on the capture session's serial queue
        dispatch_async(self.sessionQueue, ^{
            CGPoint tempTint = [(AVCaptureFigVideoDevice *)device temperatureAndTintValuesForDeviceWhiteBalanceGains:gains];
            
            // Dispatch back to main queue for UI updates
            dispatch_async(dispatch_get_main_queue(), ^{
                // Update your UI with tempTint values here
            });
        });
    } 
    // Handle other custom contexts here...
    else {
        // Let superclass handle unrecognized contexts to avoid system KVO issues
        [super observeValueForKeyPath:keyPath ofObject:object change:change context:context];
    }
}

3. Prevent Duplicate Observer Registration #

Modify addObservers to remove existing observers before adding new ones, ensuring you never have duplicate registrations even if viewWillAppear runs multiple times:

- (void)addObservers {
    // Remove existing observers first to avoid duplicates
    [self removeObservers];
    
    // Add all your observers as before
    [self addObserver:self forKeyPath:@"sessionRunningAndDeviceAuthorized" options:(NSKeyValueObservingOptionOld | NSKeyValueObservingOptionNew) context:SessionRunningAndDeviceAuthorizedContext];
    [self addObserver:self forKeyPath:@"stillImageOutput.capturingStillImage" options:(NSKeyValueObservingOptionOld | NSKeyValueObservingOptionNew) context:CapturingStillImageContext];
    // ... rest of your observer additions
}

4. Verify Notification Center Cleanup #

Double-check that [self runtimeErrorHandlingObserver] is properly managed. If this is a separate observer object, store it as an instance variable instead of re-creating it in removeObservers to avoid accessing a deallocated object.

Additional Debugging Tips #

• Enable the Zombies Instrument to catch deallocated object access during KVO callbacks
• Add logging to track when addObservers/removeObservers are called, and check for mismatched registration counts
• Test on devices with older iOS versions (if applicable) to rule out API behavior changes

内容的提问来源于stack exchange，提问作者BlackRock