Solving AVFoundation FigCaptureSourceRemote err=-17281 on iOS 26 — reliable workaround for repeated camera initialization

While working on a heart rate measurement app (photoplethysmography via camera), we faced systematic err=-17281 (FigCaptureSourceRemote) issues on real devices starting from iOS 17+, and the problem became more noticeable after iOS 26. The error often appeared during AVCaptureSession initialization or when restarting capture, especially under high frame rates (30-60 FPS) and frequent foreground/background transitions. Root cause (our understanding):

Camera hardware/session not fully released after previous use Race conditions between session teardown and new setup Changes in AVFoundation capture pipeline in recent iOS versions

Our solution: Instead of blocking delays, we implemented asynchronous retry logic with explicit hardware readiness check via AVCaptureDevice.lockForConfiguration().

Answered by Frameworks Engineer in 892450022

Hi, thank you for mentioning this.

We believe this has been fixed in iOS 27. Are you still seeing this issue in Seed 1?

I think I have a related problem in my code. Please see this link: https://developer.apple.com/forums/thread/822717

I'd like to understand better how your solution works and how you are using lockForConfiguration as a hardware readiness check.

Hi, thank you for mentioning this.

We believe this has been fixed in iOS 27. Are you still seeing this issue in Seed 1?

If you're still seeing this logging in Seed1, please do file a report at feedbackassistant.apple.com

Solving AVFoundation FigCaptureSourceRemote err=-17281 on iOS 26 — reliable workaround for repeated camera initialization
 
 
Q