Sudden crash on launch from all TestFlight builds

Question

Sam NZ OP

Created Dec ’21

Replies 35

Boosts 1

Views 29k

Participants 40

We've been getting a crash on launch starting today from all processed builds from TestFlight.

An identical build we submitted the day before yesterday is crashing on launch too.

Specifically the issue is:

Exception Type: EXC_CRASH (SIGABRT)
Exception Note:
EXC_CORPSE_NOTIFY
Termination Reason: DYLD 1 Library missing
Library not loaded: @rpath/libswift_concurrency.dylib
"/usr/lib/libswift_Concurrency.dylib' (no such file)
(terminated at launch; ignore backtrace)
(no such file)

We're pretty concerned and after aggressive testing we don't think we're the root cause.

Answered by Apple Developer Support in 698119022

Thank you for reporting this issue. We are currently working to resolve this. In the meantime, a workaround can be found in the Xcode 13.2 Release Notes. (Bug number 86349088)

Answer 1

ManyLattice OP

Dec ’21

I can't upload macOS app in AppStoreConnect. Every time error what "libswift_Concurrency.dylid"contain unsupported content

Xcode 13.2.1

Answer 2

nexus2107 OP

Dec ’21

I still have a crash on iOS12.5.5 related to libswift_Concurrency.tbd even using Xcode 13.2.1. So, I switched back to Xcode 13.1

Answer 3

luoxiao1120 OP

Dec ’21

I can't upload the app to appstoreconnect, and I keep getting this error. The application has been unable to update, very annoying. At present, I don't know how to solve this problem. Hope someone tells me.

Xcode 13.2.1 (13C100)

WX20211227-234047@2x.png

Answer 4

sebastien-tribu OP

Dec ’21

We also had this problem and updating to Xcode 13.2.1 solved this issue.

From https://developer.apple.com/documentation/xcode-release-notes/xcode-13_2_1-release-notes

Resolved Issues

Fixed an issue where apps built with Xcode 13 or Xcode 13.1 sometimes crashed at launch with an error reporting that the libswift_Concurrency.dylib library was not loaded. This only affected apps that used Swift Concurrency features (such as async/await), deployed to iOS prior to 15, tvOS prior to 15, or watchOS prior to 8, and had bitcode enabled. (86349088)

Hope this helps

Answer 5

SeongsooSim OP

Jan ’22

Xcode: 13.2.1, iPhone: 14.2 and 14.8 without "Debug executable" causes 100% crash. It's OK when I checked the "Debug executable".

I created new iOS project and added a button on ContentView and press the button.

Task("Hello, world!")
    .padding()
Button("Run task") {
    Task.init {
        print("run task")
    }
}

Answer 6

mottods OP

Jan ’22

What about published apps? Our app is available from the app store. I installed it and it crashed instantly. So what should we do now? Should we resubmit with Xcode 13.2.1 or should we wait for Apple to resolve the issue? Any idea?

Thanks,

Answer 7

rajendrak OP

Jan ’22

This is marked as resolved in Xcode 13.2.1, but still getting issue. I have disabled bitcode enabled to get rid of this issue until resolves.

Answer 8

sergd2005 OP

Mar ’22

Short answer - use Fastlane to distribute via Testflight. Long answer - We had an issue with the app on iOS 14.6. XCode Version 13.3 (13E113). When distributed via Fastlane to Firebase - the app works fine. Running the app from Xcode works fine too. But when we distributed via Testflight using Xcode - app crashes at launch. No crash logs. I tried including libswift_Concurrency.tbd, disabling bitcode etc. Nothing helped. Finally I tried fastlane and it works! So yeah I assume there is some bug in exporting from archive in Xcode.

Answer 9

N. Holzschuch OP

Apr ’22

Hi, I have the same symptoms: the app crashes immediately on all devices running iOS 14. I have tried everything recommended in this thread (disabling bitcode, adding libswift_Concurrency, adding "-Wl,-weak-lswift_Concurrency -Wl,-rpath,/usr/lib/swift" to "other linker flags"...) but it still crashes.

Answer 10

rethgil2 OP

May ’22

XCODE 13.4 STILL THE SAME PROBLEM! Adding "-Wl,-weak-lswift_Concurrency -Wl,-rpath,/usr/lib/swift" DIDN'T WORK ONLY DISABLE BITCOD works but it's not a good solution.

What's going on?