iOS 17 camera capture assertions and issues

Question

Created Feb ’24

Replies 4

Boosts 1

Views 1.5k

Participants 5

Hello,

Starting in iOS 17, our application started having some issue publishing to our video session. More specifically the video capture seems to be broken in some, but not all sessions. What's troubling is that we're seeing that it fails consistently every 4 sessions.

It also fails silently, without reporting any problems to the app. We only notice that there are no frames being rendered or sent to the remote devices.

Here's what shows-up in the console:

<<<< FigCaptureSourceRemote >>>> Fig assert: "! storage->connectionDied" at bail (FigCaptureSourceRemote.m:235) - (err=0) <<<< FigCaptureSourceRemote >>>> Fig assert: "err == 0 " at bail (FigCaptureSourceRemote.m:253) - (err=-16453)

Anyone seeing this? Any idea what could be the cause? Our sessions work perfectly on iOS16 and below.

Thanks

Boost

Answer 1

jayhxmo OP

Apr ’24

Have you found any leads or solutions to this? Experiencing the same issue.

0

Answer 2

DavidL1 OP

Sep ’25

For anyone stumbling over this: Camera worked again after restarting the phone.

0

Answer 3

zzmSnail OP

Oct ’25

I get this warning too in ios 26, but my camera works fine, I want to know how to fix this warning, does some know?

0

Answer 4

statemachinejunkie OP

4m

I am seeing these errors as well. In between each session, I completely release and re-create the capture session to make sure I'm not holding onto any resources but it doesn't make a difference. What is the common wisdom on how to deal with this apparent OS issue? Is it advised to keep the original capture session around for the lifetime of the application? We currently do not do this because our camera is a USB device that may be swapped out for different models with different data formats, etc. In this case, the user has to stop and re-start our application in order to proceed, which is not ideal.

0