Occasional dyld __abort_with_payload crashes

In Apple's crash organizer, I'm seeing a handful of crash reports come in. It doesn't appear to be a widespread issue, but keeps happening now and again.


Exception Type:  EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note:  EXC_CORPSE_NOTIFY
Termination Description: DYLD, Library not loaded: @rpath/libswiftCoreGraphics.dylib | Referenced from: /var/containers/Bundle/Application/7208AD66-5D56-4973-88A9-8D22D7E541DB/myapp.app/myapp | Reason: no suitable image found.  Did find: | /private/var/containers/Bundle/Application/7208AD66-5D56-4973-88A9-8D22D7E541DB/myapp.app/Frameworks/libswiftCoreGraphics.dylib: code signature invalid for '/private/var/containers/Bundle/Application/7208AD66-5D56-4973-88A9-8D22D7E541DB/myapp.app/Frameworks/libswiftCoreGraphics.dylib' |
Triggered by Thread:  0
Thread 0 Crashed:
0   dyld                          0x00000001004d5cbc __abort_with_payload + 8
1   dyld                          0x00000001004d5668 abort_with_payload_wrapper_internal + 100 (terminate_with_reason.c:71)
2   dyld                          0x00000001004d5694 abort_with_payload + 12 (terminate_with_reason.c:93)
3   dyld                          0x00000001004b4514 dyld::halt(char const*) + 320 (dyld.cpp:4487)
4   dyld                          0x00000001004b69a8 dyld::_main(macho_header const*, unsigned long, int, char const**, char const**, char const**, unsigned long*) + 4072 (dyld.cpp:6110)
5   dyld                          0x00000001004b1044 _dyld_start + 68


A couple of versions ago, I saw a similar crash with libswiftCoreMedia.dylib instead of Core Graphics.


Any thoughts on what I can do to mitigate this or stamp it out?

Up vote post of bpapaattheskimm Down vote post of bpapaattheskimm
6.1k views
Posted by
bpapaattheskimm
Reply

  • Hello, I also have a similar crash problem, the stack log is as follows /Users/chuqiangsheng/Downloads/CCjJD-iYt32hBysll5nxvC.xccrashpoint/Filters/Filter_CCjJD-iYt32hBysll5nxvC-1031496437-com.bocichina.e-com.apple.platform.iphoneos-com.apple.platform.iphoneos-6.03.040-Any/Logs/2023-07-20_09-17-31.2552_+0800-5e7d30ba1839a06585d9188df127833f3710294a.crash

    —
    yaoyue
Add a Comment

Replies

Hi,

I think I have just met this problem. I am using El Capitan 10.11.6 and Xcode 7.3.1. I started work with my project using 7.3.1 and Swift 2 (2.3, I think), and up until today have had no problems with simulator or iPhone device as long as I copied new SDK from latest version Xcode, Today the app stopped working on my phone, so I tried to get it going again, by running through Xcode and I got the "dyld: library not loaded: @rpath/ ...... Reason: no suitable image found. .....". The app still works with the simulator. As far as I am aware I did nothing before the failure, everything had been working fine - no updates or changes had been made since I last ran the app on my phone (SE iOS 10.3.2). I have looked at other comments (many from 2015), but did not really see a solution and most seemed to be much more complex apps where the problem occured when some change was made - this was not the case with me. No idea how to progress - any help please!


Posted by
LesJay
Up vote reply of LesJay Down vote reply of LesJay
Add a Comment

I spent about 6 hours yesterday trying to sort out this problem - unsuccessful. Today I downloaded the Apple WWDR certificate, but when I tried to install it I was not sure where to install it so tried to run through Xcode again after saying a prayer and doing a 'clean' (again, I think). I ran the app through the simulator first and all OK, then tried through my iphone SE device and it ran with no problem!! But really, what is going on - first it will not work on the device, for no apparent reason, and then it starts working again, for no apparent reason. If this was a car would I think this acceptable - you bet your life I wouldn't!!

Posted by
LesJay
Up vote reply of LesJay Down vote reply of LesJay
Add a Comment

I ran into this problem as well and spent a few hours trying to find a solution and this response helped me to the right direction. This solved the problem with me: checked the Apple WWDR certificate to use system defaults in the trust section, cleaned the project and that did the trick!

Posted by
ppahka
Up vote reply of ppahka Down vote reply of ppahka
Add a Comment

I have also same proble. i have tried with WWDR certificate. but still getting error. please help me. i am working on it from 1 and half day.

Posted by
Prashant_Empiric
Up vote reply of Prashant_Empiric Down vote reply of Prashant_Empiric
Add a Comment