Recurring FigXPCUtilities / FigCaptureSourceRemote err=-17281 logs when using AVCaptureVideoDataOutput on iOS 26.x

Question

Created Dec ’25

Replies 3

Boosts 2

Participants 3

Hi everyone,

I’m seeing recurring internal AVFoundation camera logs on iOS 26.2 and I’m trying to understand whether this is expected behavior or a regression in the capture pipeline.

These logs appear shortly after starting an AVCaptureSession, while video frames are being delivered, and also when the camera is stopped or the capture session is torn down.

<<<< FigXPCUtilities >>>> signalled err=-17281 at <>:302 <<<< FigCaptureSourceRemote >>>> Fig assert: "err == 0 " at bail (FigCaptureSourceRemote.m:569) - (err=-17281)

Even in this clean, minimal setup, the same logs appear on iOS 26.2

The exact same logic did not produce these logs on iOS 18.x.

To rule out issues caused by my own code, GPT created a minimal SwiftUI example from scratch.

My primary interest is to perform real-time processing on the video frames delivered by the camera (via AVCaptureVideoDataOutput), for tasks such as analysis, computer vision, or custom frame handling, while simultaneously displaying the live preview.

Thanks in advance for any insight.

Example Code

Boost

Answer 1

FraUlloa OP

Jan ’26

up

1

Answer 2

hoosierdev OP

1d

Similar issue here when starting an ARSession.

iOS 26.3.1 on an iPhone 16 Pro. No issues running the same app on an iPhone 12 on iOS 18.6.2

`(Fig) signalled err=-12710 at <>:601
<<<< FigXPCUtilities >>>> signalled err=-17281 at <>:308
<<<< FigCaptureSourceRemote >>>> Fig assert: "err == 0 " at bail (FigCaptureSourceRemote.m:569) - (err=-17281)`

0

Answer 3

DTS Engineer OP

Apple

1d

Thanks for this interesting post! I'm not an expert on that field nor that API. Hope one of the engineers on that team can jump into this thread for better info.

These specific FigXPCUtilities and FigCaptureSourceRemote logs are almost certainly benign internal framework noise rather than a regression or a flaw in your capture pipeline.

Looking up the err=-17281 is a CoreMedia error code that, without knowing here, typically points to a minor XPC synchronization hiccup, a port invalidation, or an asynchronous state mismatch during the setup or teardown of the capture session? I believe this logs are for information only and should be removed.

Code paths that silently recovered in older iOS versions often have their log levels elevated in newer releases (or beta releases), resulting in console spam.

If your AVCaptureVideoDataOutputSampleBufferDelegate is successfully receiving CMSampleBuffer frames and your preview layer is rendering smoothly. You can safely ignore these logs.

If you want to temporarily hide this console spam in Xcode, you can go to Edit Scheme -> Run -> Arguments, and add an Environment Variable OS_ACTIVITY_MODE set to disable. Be aware this disables all os_log output, including your own. I won’t recommend that.

You can always file a bug to request to remove that log from the console.

Albert Pascual   Worldwide Developer Relations.

0