iOS 15 dyld Crash

App & System Services Core OS iOS Debugging

And0Austria OP

Created Sep ’21

Replies 17

Boosts 1

Views 11k

Participants 13

Hello,

I get a lot of crashlogs in the Xcode organizer on iOS 15 all related to dyld. Does anybody has the same issue or any idea what could be the problem? Attached is the Crashlog.

Following error is shown:

Kernel Triage: VM - Fault was interrupted VM - Didn't get back data for this file VM - Fault was interrupted

file.crash

Answered by stlee in 700990022

hi folks,

do we have any solution regarding this type of crash? seeing this on our app where the crash happens to some of the users using iOS 15.x

for folks who have the similar issue, wondering if you could list down the list of frameworks that you are using? suspect that might be one of the framework that we were using cause this issue

Boost

iharfrombratislava OP

Aug ’22

We're experiencing thousands of NO_CRASH_LOG crashes like the one described in this thread. This all started with iOS 15 release. When you open a .crash file it shows just a couple of dyld calls and then EXC_CORPSE_NOTIFY with a system watchdog killing the app during launch after 1 minute of inactivity. Binary images section only contains .dyld and sometimes a few other system .dylib-s - no modules from our app. I'm attaching an example here? I filed a bug to Apple via feedback.apple.com, but they replied that they need system logs from affected devices, which we cannot provide because the issue (according to the Apple's Xcode reporting system) happens on our AppStore users devices, but we can't reproduce it by ourselves. My radar is still in "open" status bus since then there hasn't been any activity. I know that a lot of people also reporting this, and there're also a lot of forum discussions, eg this one: https://developer.apple.com/forums/thread/710463 Does anybody have an answer for this?

2022-07-24_11-09-56.9474_-0500-131fd7580c89bb6093b56e883161e3bb6182838c.crash

ivasilev@productiveedge.com OP

Nov ’22

UPDATE: after iOS 16 came out, presumably due to the users updating to it from earlier versions, the number of these odd crashes gradually reduced to almost zero now.