'dyld`__abort_with_payload: Without an error message

When I start my app with Xcode, I have a crash, but without an error.

The app is just stopping on this thread:

What can I do to have more information about the issue?

ios xcode xcode8

Solution 1:^[1]

If you are using custom frameworks, you need to put it inside the "Embedded Binaries" section located in the Xcode project under the tab Target / General.

Solution 2:^[2]

For me a simple Clean and Rebuild sorted it out.

Solution 3:^[3]

This problem appeared after a system update up to macOS 10.15.2 beta (Catalina). Disabling "Thread Sanitizer" solved the issue (Xcode 11.2). Now I can't use Thread Sanitizer and have to wait for the next OS update.

Solution 4:^[4]

Adding the framework to the embedded binary asset list fixed this. Here is what the setup of a foreign framework looks like in final form in the Xcode GUI as an Embedded Framework (Xcode 9.2, personally I like a visual breadcrumb trail better ;-) ):

Did Apple intentionally crash the runtime to somehow tell the developer about the problem that you cannot use non-Apple frameworks as simply linked frameworks in iOS development? It would be better to have it come up as a build error I would think... with a button that said "move it!"

The use of Embedded Binaries keeps the end user from having to add the Framework independently of your app (or have you do with an installer). In the case of the iPhone (iOS), that is impossible, but on macOS, it is possible, but it can get messy fast.

For the end user, it is much nicer to simply drag and drop an app to install it on macOS, which is where embedded becomes a benefit. Embedding also avoids the classic "DLL conflicts" of having external versions of your framework to manage. (Disk space is cheap, but my customer's time is precious.)

Solution 5:^[5]

I fixed the error in my project just now!

If you are using the Swift framework in an Objective-C project, I advice you to change the build settings.

Set the Always Set Embed the Swift Standard Libraries option to Yes. Like this:

Solution 6:^[6]

It was finally solved!

Making the framework "optional" instead of "required" worked for me.

Solution 7:^[7]

In Xcode 11.1, turn off Do not Embed in Embed & Sign is a nice option.

_{Credit: mkonovalov's answer and William Cerniuk's answer}

Solution 8:^[8]

To answer the original question "What can I do to have more informations about the issue?", this Apple forum thread provides a very simple tip: simply run your crashing app outside Xcode (i.e., stop it from Xcode, then run it manually on your device).

This will produce a crash log containing more details about what happened. You can then review this log from the Xcode Window menu ? Devices and Simulators ? View Device Logs.

Solution 9:^[9]

Unchecking "Guard Malloc" in diagnostics worked for me.

Solution 10:^[10]

Continue the execution to see if any message shows up in debugger such as "MyFramework.framework" not found. If that is the case, follow this question: OS X Framework Library not loaded: 'Image not found' For me Amos Joshua's answer worked.
Make sure you have added your binaries through "Embed Binaries" section.
Make sure you have enabled signing of frameworks in build phase section.
Make sure the embedded frameworks are not symlinks.
You can make the linked frameworks optional instead of required in "Link binary with libraries" phase. This will tell iOS to not look for these frameworks during launch. But anyway you need to fix the errors to use those frameworks!
Check if all the info.plist entries are good. In my case, I was using a Mac info.plist file for iOS. It was looking for some xib file which was not present in the iOS project.
Do a clean and build after any such change. This is required because Xcode does not copy/change these files if they already exist.
Remove the app from iPad and then install. Same reason as 7.

Solution 11:^[11]

I had just missed applying the "Privacy - Camera Usage Description" in the info.plist file.

Solution 12:^[12]

I faced the same issue with Xcode 11.3 and macOS v10.15.2 (Catalina) . The app was running well on the device, but not in the simulator. It seems there is an issue with the simulator and the workaround is to disable Thread Sanitizer.

Refer to Xcode 11.3 simulator SIGABRT on launch.

Solution 13:^[13]

I encountered an error with the same signature (my project was in Objective-C) and discovered I had forgotten to link with the appropriate framework. The error message in the debug log that led to finding the error was:

dyld: Symbol not found: OBJC_CLASS$_SFSafariViewController

For my specific error, adding SafariServices.framework in the Targets ? Build Phases ? "Link Binary With Libraries" resolved the issue. While you probably don't have the same specific error and resolution, checking the debug log for clues is useful.

Solution 14:^[14]

I had a similar issue that was resolved by a missing permission specification in plist (as weird as it is...).

I've tried to use AVCaptureDevice and it just crashed at starting (my app was very minimal).

Adding Privacy - Camera Usage Description to the info.plist file solved it for me.

Solution 15:^[15]

Sometimes it happens when you use system frameworks that are accessible only from a later iOS version than your target version. It might be fixed by marking this linked framework as optional.

For example, a project targeted on iOS 11 and being using AuthenticationServices for the iOS 12 AutoFill feature will crash on iOS 11 in the described way.

Solution 16:^[16]

I've had this situation after updating Xcode to v10.2.1 and Swift to v5.0.

If you are using Carthage + RxSwift, the new RxSwift uses RxRelay.framework. You should go to your /Carthage/Build directory find that framework and drag it to your project. Don't forget also add it to your carthage copy-frameworks script: $(SRCROOT)/Carthage/Build/iOS/RxRelay.framework

It was resolved thanks to fred's answer.

Solution 17:^[17]

I was facing the same issue. Setting 'Always Embed Swift Standard Libraries' to Yes in Build Settings of my target worked for me.

Solution 18:^[18]

If you use the Carthage build framework, after dragging the framework to your project, you should add it to General/Embedded Binaries.

Solution 19:^[19]

I found the right way to resolve it.

Make sure the AppleWWDRCA.cer is set to the system default mode, and then it will work:

Enter image description here

Solution 20:^[20]

If you're using a framework written in Swift in an Objective-C application, you need to include the Swift toolchain in the app that consumes the framework.

The way I've found to do this is to create a dummy Swift file in the app, so that Xcode recognizes Swift and appropriately adds it to the project. You can then delete the dummy file.

Solution 21:^[21]

Also if you are using custom frameworks, make sure you set the Mach-O type to static library. I read somewhere that iOS doesn't allow dylib. Anyway, this worked for me.

Solution 22:^[22]

To add to the long list of encounters with this error, it occurs when I am on Xcode 12.2 Beta 2 deploying to my Mac running macOS v10.15.5 (Catalina) with the deployment target set to macOS v11.0 (Big Sur).

This situation happened because I was trying out the Mac Catalyst Tutorial app on adding a SideBar. Switching the target to macOS v10.15.5 eliminated the error and launched the app properly.

Solution 23:^[23]

I faced this issue on iOS 14.5 when playing/implementing ATT (App Tracking Transparency) and have yet to add a usage description in file info.plist on why user tracking is needed.

The app crashes whenever the settings "Allow Apps to Request to Track" was enabled (when disabled, everything worked well).

The crash in Xcode provided no clues, except

libsystem_kernel.dylib`__abort_with_payload: (SIGABRT)
CoreSimulator 757.5 - Device: iPhone 11 (29AD27B2-6EC0-4B9C-8C8C-C5450695A19C) - Runtime: iOS 14.5 (18E182) - DeviceType: iPhone 11

Using the answer from fred's answer and getting the crash log from the actual device yielded this clue which was extremely helpful.

Exception Type:  EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note:  EXC_CORPSE_NOTIFY
Termination Reason: TCC, This app has crashed because it attempted to access privacy-sensitive data without a usage description. The app's Info.plist must contain an NSUserTrackingUsageDescription key with a string value explaining to the user how the app uses this data.
Triggered by Thread:  1

Solution 24:^[24]

I fixed it by changing "Embed & Sign" to "Embed without Signing" under General > Frameworks, Libraries and Embedded Content.

Solution 25:^[25]

I didn't think this applied to me because I wasn't using the camera, but it did.

Many answers reference adding a Usage Description to Info.plist. I didn't know there are many more cases where a usage description is necessary (besides just the camera), see this link.

The link lists these services as needing a usage description or will cause this error:

Calendar, Contact, Reminder, Photo, Bluetooth Sharing, Microphone, Camera, Location, Heath, HomeKit, Media Library, Motion, CallKit, Speech Recognition, SiriKit, and TV Provider.

Add an entry to Info.plist, start typing "Privacy" as the key, and you will see all the available options pop up.

Solution 26:^[26]

I've just had the same issue and the reason why was due to the fact that I've revoked my Developer Certificates and created new ones with Xcode 10, after a fresh macOS v10.14 (Mojave) update (for some reason, it deleted all login credentials and outdated some keychain certificates).

So, all I had to do was to remove the installed apps from my device and run them through Xcode again, in order for it to install the right new Provisioning Profile in my device :)

Solution 27:^[27]

Actually, I had the issue with Xcode 11.3.1 and Thread Sanitizer was already turned off as mentioned in previous answers.

In my case, the issue was I used to have different Xcode versions in my Application folder like this:

/Applications/xcode11.3.1/Xcode.app
/Applications/xcode11.3/Xcode.app
/Applications/xcode10.1/Xcode.app

and

/Applications/Xcode.app - was 11.2

The build system looks on the /Applications/Xcode.app file by default. So bringing Xcode 11.3.1 to the /Applications/Xcode.app finally resolve the problem.

Solution 28:^[28]

The same issue happened with me. I had iOS 14 Beta and the problem was fixed when I updated it to the official version.

Solution 29:^[29]

I have fixed my error in my project.

I checked the other threads when the error happened. I found my error is about the camera.
Add the Camera privacy in the Info.plist file.
1. Open the info.plist file.
2. Add a new key called "Privacy - Camera Usage Description" and enter a string that describes why the app need camera. The describes will display when your app need to use the privacy.

Solution 30:^[30]

I had this issue and didn't have success with the answers. I was using a custom framework that would connect with Bluetooth devices. So the crash was happening because I had missed applying the "Privacy - Bluetooth Always Usage Description" in the info.plist file.

Check all your permissions fields are set up in the p-list file.

Sources

This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.

Source: Stack Overflow

Solution	Source
Solution 1
Solution 2	Peter Mortensen
Solution 3	Peter Mortensen
Solution 4	Peter Mortensen
Solution 5	Peter Mortensen
Solution 6	Peter Mortensen
Solution 7	Peter Mortensen
Solution 8	Peter Mortensen
Solution 9	Peter Mortensen
Solution 10	Peter Mortensen
Solution 11	Peter Mortensen
Solution 12	Peter Mortensen
Solution 13	Peter Mortensen
Solution 14	Peter Mortensen
Solution 15	Peter Mortensen
Solution 16	Peter Mortensen
Solution 17	Arpit Panda
Solution 18	Peter Mortensen
Solution 19	Peter Mortensen
Solution 20	Peter Mortensen
Solution 21	Peter Mortensen
Solution 22	Peter Mortensen
Solution 23	Peter Mortensen
Solution 24	chocolate cake
Solution 25	Minimistro
Solution 26	Peter Mortensen
Solution 27	Peter Mortensen
Solution 28	Peter Mortensen
Solution 29	Peter Mortensen
Solution 30	Peter Mortensen

'dyld`__abort_with_payload: Without an error message

Solution 1:[1]

Solution 2:[2]

Solution 3:[3]

Solution 4:[4]

Solution 5:[5]

Solution 6:[6]

Solution 7:[7]

Solution 8:[8]

Solution 9:[9]

Solution 10:[10]

Solution 11:[11]

Solution 12:[12]

Solution 13:[13]

Solution 14:[14]

Solution 15:[15]

Solution 16:[16]

Solution 17:[17]

Solution 18:[18]

Solution 19:[19]

Solution 20:[20]

Solution 21:[21]

Solution 22:[22]

Solution 23:[23]

Solution 24:[24]

Solution 25:[25]

Solution 26:[26]

Solution 27:[27]

Solution 28:[28]

Solution 29:[29]

Solution 30:[30]