Ahh, that was an interesting explanation. Thank you for the insight and the suggestion. We will try it and see how it goes, really appreciate you taking the time to help as always, thank you !

Right. But the presence of a third-party crash reporter undermines the trustworthiness of Apple crash reports. I talk about this in Implementing Your Own Crash Reporter, and there was a really good (well, bad)-: example of this phenomenon in this recent thread. I see, thanks for sharing that. I'll look into it in more detail later with the team. Sorry about that. This is a known bug. The workaround, as explained in Posting a Crash Report, is to change the extension to .txt and attach that. Got it, I am able to attach the .ips crash report below now, thanks for the workaround. crash-2025-08-21-214703.txt

I've attached the .ips crash report in FB17775979 since I cannot upload it here. Hope it can help with the investigation and there is any insight that can be shared with me. Truly weird crash as it seems we are the only one who faced this issue as I didn't found any other related thread to this yet.

Hi, after few months, I haven't been able to solve this yet but apparently our Test Engineer able to reproduce this crash (accidentally) recently so I was able to ask them for the .ips crash report. I'd like to attach the file here, but I cannot select it as the file seems disabled from the upload menu. Any suggestion ?

Do you have any .ips (JSON format) crash reports? Unfortunately, I don't have them. Also, you’re using a third-party crash reporter (see thread 4 in your first crash report), which isn’t something I generally trust. See Implementing Your Own Crash Reporter for an explanation as to why. Yes, we use third party crash reporter to help monitor our release in a dashboard but the crash reports I shared here and in the bug report are all coming from Xcode organizer crash reports. Usually they both have similar stack traces but I think Xcode organizer crash reports is more detailed (like they include Exception Type and Subtype).

Anyone experiencing the same crash please try @SepCode and @CallumFromOz approach by retaining and reuse the AVPictureInPictureController for the whole lifetime of your app (never dealloc it). I tried the same approach and the crash did disappear in my case. I am not sure if this is intended or not by Apple but for now this solution can help to prevent further crashes.

It's been a while, but I've checked that this specific crash has been solved in iOS 18 !

It's my pleasure ! Thanks for taking the time to say this.

Ahh, thanks for sharing that ! Well, I guess it's clear now that we can only wait for the update on our bug report or see if future iOS version will include the fix. I appreciate the help given, thanks !

If anyone ever come across this thread and having the same issue, we got a response from Apple DTS in our bug report saying that this is memory shortage issue. Hope it helps. NSSQLiteErrorDomain=13 is error number 13 from sqlite3.h which is SQLITE_FULL. The device is out of disk space.

Do you have any JSON crash reports for this? That is, any .ips files. If you do, please post one here, or add it to your bug report and let me know here. Unfortunately, we don't. This crash is very similar to the one discussed here. Unfortunately, that thread doesn’t have a great resolution. We’ve definitely fixed some bugs that result in crashes like this, but that’s obviously not the full story. I see, so something similar did happen in the past already. Your third-party crash report references CFHost. Are you calling that directly? No, I've checked and found no reference to CFHost in our codebase. We also never call CFNetwork APIs directly either.

Noted, will do that. Thanks !

Got it. So I tried to create a new thread here but I was able to attach the crash report just fine. Now I am more confused why it didn't work few days earlier. The only case I can think now is someone maybe accidentally mess up the logic earlier then fixed it, that's why it works now.

You were right, I was able to upload it here. Actually last time, I only tried to upload it when trying to create the initial post, not through reply section. I wonder if that could be the factor to this issue or the logic used there should be the same with reply section ?

Test to upload crash report crash-log-iOS-17.crash