xcode14:Library not loaded: /usr/lib/swift/libswiftCoreGraphics.dylib

  • Facing the same issue. Will leave a reply with the details we have noticed so far.

  • I have the same problem with app submitted to TestFlight and running on iOS10.3.4. using xCode 13.4.1 to build App run fine started from xCode (debug or release mode) on the device App run fine on device under iOS 15.7 even with TestFlight Problem is there since at least 01/09/2022

    Feedback : FB11529856

  • Can I please ask the question author to not mark it as accepted/resolved so that it does not affect the visibility of the issue?

Apple Recommended

  • Glad to hear that!

    I have a follow-up question. If we still use Xcode 13.4.1 and enable bitcode, then we upload it to the App Store later when Xcode 14.1 is released, would the benefit of bitcode still remain on that build? In our previous app releases, turning on bitcode would reduce the App Launch time by a couple of hundred milliseconds.

    Thanks!

  • Hi, if I've updated to Xcode 14.1 RC, should I enable bitcode or not?

  • Disabled bitcode in Xcode 13.4.1 solved my problem, but I wonder that when I update to Xcode 14.1 in future, could I enable bitcode? and what's bitcode is deprecated in Xcode 14 mean, is that the same whether you set it enabled or disabled? Thank you.

Replies

We have also been experiencing this issue. The workaround suggested by Apple did not fix everything, as our project - like many others - uses Cocoapods and other frameworks. Each of these needed to be updated as well, and the issue seemed to be resolved.

Is it even worth it to turn on bitcode nowadays? Is there any advantage left? Since bitcode is not supported anymore on Xcode 14.

Library not loaded: /usr/lib/swift/libswiftCoreGraphics.dylib  Referenced from: /private/var/containers/Bundle/Application/***/***/Frameworks/SnapKit.framework/SnapKit

1.Build Setting ->Other Link Flags Add configuration -Wl,-weak-lswiftCoreGraphics; 2.If have cocopods,found the error framework like ” SnapKit.framework“ do the same Add configuration -Wl,-weak-lswiftCoreGraphics;

After multi-person testing, the crash problem can be solved

  • Glad to hear that!

    I have a follow-up question. If we still use Xcode 13.4.1 and enable bitcode, then we upload it to the App Store later when Xcode 14.1 is released, would the benefit of bitcode still remain on that build? In our previous app releases, turning on bitcode would reduce the App Launch time by a couple of hundred milliseconds.

    Thanks!

  • Hi, if I've updated to Xcode 14.1 RC, should I enable bitcode or not?

  • Disabled bitcode in Xcode 13.4.1 solved my problem, but I wonder that when I update to Xcode 14.1 in future, could I enable bitcode? and what's bitcode is deprecated in Xcode 14 mean, is that the same whether you set it enabled or disabled? Thank you.

We're facing quite similar issue.

Short brief of our situations:

  • we pushed app to appstore connect at 08.11.2022
  • app was built using Xcode 13.4.1 (Build version 13F100)
  • bitcode enabled

Based on latest feedback I understand that apps that are built using the XCode 13.x but published after the XCode 14.1 release should work fine. Anyway we're facing the crashes that occur on devices with iOS 11.x (11.1, 11.2.5)

Crashlog:

Incident Identifier: A0A546D9-A226-40FA-A274-D3F233CEDE5F
Hardware Model:      iPhone7,1
Process:             myapp [1156]
Path:                /private/var/containers/Bundle/Application/90DA7BAA-579C-471B-B0FF-39336888B2A8/myapp.app/myapp
Identifier:          com.myapp.app
Version:             1667918418 (9.6.1)
Code Type:           ARM-64 (Native)
Role:                Foreground
Parent Process:      launchd [1]
Coalition:           com.myapp.app [480]


Date/Time:           2022-11-13 12:43:12.9491 +0700
Launch Time:         2022-11-13 12:43:12.4916 +0700
OS Version:          iPhone OS 11.2.5 (15D60)
Baseband Version:    6.30.04
Report Version:      104

Exception Type:  EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note:  EXC_CORPSE_NOTIFY
Termination Description: DYLD, Library not loaded: /usr/lib/swift/libswiftCoreData.dylib | Referenced from: /var/containers/Bundle/Application/90DA7BAA-579C-471B-B0FF-39336888B2A8/myapp.app/myapp | Reason: image not found
Triggered by Thread:  0

Thread 0 Crashed:
0   dyld                          	0x00000001014d2f48 __abort_with_payload + 8
1   dyld                          	0x00000001014d271c abort_with_payload_wrapper_internal + 100 (terminate_with_reason.c:71)
2   dyld                          	0x00000001014d2748 abort_with_payload + 12 (terminate_with_reason.c:93)
3   dyld                          	0x00000001014a8498 dyld::halt(char const*) + 312 (dyld.cpp:3824)
4   dyld                          	0x00000001014ab714 dyld::_main(macho_header const*, unsigned long, int, char const**, char const**, char const**, un... + 7376 (dyld.cpp:6202)
5   dyld                          	0x00000001014a521c _dyld_start + 68

Thread 0 crashed with ARM Thread State (64-bit):
    x0: 0x0000000000000006   x1: 0x0000000000000001   x2: 0x000000016f79a520   x3: 0x0000000000000092
    x4: 0x000000016f79a120   x5: 0x0000000000000000   x6: 0x0000000000000000   x7: 0x0000000000000a60
    x8: 0x0000000000000020   x9: 0x0000000000000009  x10: 0x6c504b2f38413242  x11: 0x4b2f7070612e7375
   x12: 0x20200a73756c504b  x13: 0x203a6e6f73616552  x14: 0x6f6e206567616d69  x15: 0x00646e756f662074
   x16: 0x0000000000000209  x17: 0x000000008000001f  x18: 0xfffffff00f49925c  x19: 0x0000000000000000
   x20: 0x000000016f79a120  x21: 0x0000000000000092  x22: 0x000000016f79a520  x23: 0x0000000000000001
   x24: 0x0000000000000006  x25: 0x0000000100664000  x26: 0x00000001014e6000  x27: 0x00000001014e5f88
   x28: 0x000000016f79bb20   fp: 0x000000016f79a0f0   lr: 0x00000001014d271c
    sp: 0x000000016f79a0b0   pc: 0x00000001014d2f48 cpsr: 0x00000000

Binary Images:
0x100664000 - 0x100f1bfff myapp arm64  <570e.......

@edford Do you know maybe what's the status of the potential fix for the mentioned issue?

facing similar issue

Recently released the update of our app to appstore which is crashing in upgraded user device, fresh install is working fine. Latest build is from xcode14, older build was in xcode 13.. Frustrating crash happens only in app store not in testflight for the same build. Crash happens in application didfinish launching options as soon as the application is opened. Some one help what could be the cause please

Facing the same issue, any ideas or updates?

Same here. I compile a xcframework with Xcode 14.2 and depending on the device I run, it crashes or not...

Any updates please?

  • You can see this article, I have introduce solution, but later versions of xcode should have repaired the problems, link: https://www.jianshu.com/p/7bf4c9bc43e1

Add a Comment

Yes please any update? Compiling a xcframework with Xcode 14.2 or 14.3 and it crashes depending on the device I run too. It's really not consistent and really annoying!

I have a similar issue with running Xcode 15 built app on iOS 16.6.1. The app runs fine on iOS 17.0.2, but crashes on launch on older version of iOS - did not have this issue with older versions of Xcode

dyld[26192]: Symbol not found: _$sSo24OS_dispatch_queue_serialC8DispatchE5label3qos10attributes20autoreleaseFrequency6targetABSS_AC0E3QoSVAbCE10AttributesVSo0a1_b1_C0CACE011AutoreleaseJ0OANSgtcfC
  Referenced from: <19E02EF7-C05C-3D62-88DC-AC4178A604FA> /private/var/containers/Bundle/Application/DBC3A9EB-A8F8-4AA4-B72C-C4C59D7C2B4E/Bank Greenwood.app/Bank Greenwood
  Expected in:     <E0BB294E-B630-379B-AAC8-D5C0A83A55E6> /usr/lib/swift/libswiftDispatch.dylib

but crashes on launch on older version of iOS

Depending on how old the “older version” is, this might be the issue listed under FB13097713 in the Xcode 15 Release Notes. If it’s not, I recommend that you start a thread with more details, because this thread is about a specific Xcode 14 issue.

Share and Enjoy

Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

  • Thanks for the link to the release notes.

    The target version of the app is already iOS 15.0, however I will try to figure out how to invoke the classic linker instead of the new linker as stated in the release notes to see if that makes a difference - "The classic linker can still be explicitly requested using -ld64, and will be removed in a future release."

    I have opened a TSI for this issue Case-ID: 4394375

Add a Comment