Xcode app crashes: Library not loaded
Use the launch crash report to distinguish a missing embedded framework from a build-time link failure.
The app linked a dynamic framework but the runtime could not find or load it. Read the crash report’s library name and searched paths, then check whether the correct framework is embedded in the app product for that platform.
Try these fixes in order
Read the actual dyld message
Capture the first Library not loaded line, Referenced from path, and Reason. A missing file, incompatible architecture, and code-signing rejection are different failures.
Inspect the app’s framework embedding
In the affected app target, inspect Frameworks, Libraries, and Embedded Content and its build phases. A dynamic third-party framework generally needs to be included in the final app bundle; linking alone may leave it absent at launch.
Check the built product
Inspect the built .app bundle’s Frameworks directory and compare its framework name and platform slice with the crash report. Verify a nested extension’s dependencies in its own bundle context.
Rebuild and launch on the failing destination
Correct the embed setting or dependency packaging, then rebuild and retest on the same device or simulator. Avoid copying arbitrary frameworks into the app after signing.
Interpret what you see
The crash names an @rpath framework inside your app
What it suggests: The app linked a dynamic library but may not contain it at runtime.
Next check: Inspect the built app bundle and Embed & Sign setting for that target and destination.
The framework exists locally but not in an archive
What it suggests: Debug and Release embedding settings or packaging may differ.
Next check: Inspect the exported archive and test that exact release build.
The missing path points to a system library or incompatible version
What it suggests: The binary may require a newer OS or incompatible platform.
Next check: Compare minimum deployment target, available OS, and binary platform support.
Why this happens
- A dynamic framework was linked but not embedded.
- The embedded binary is unavailable or incompatible for the launch destination.
Still not working?
If the framework is present but dyld still rejects it, preserve the full Reason and code-signing details. Apple’s crash guide explains how to diagnose the specific missing-framework report.
Official sources
These steps are based on the linked documentation and general diagnostics. BugMedic has not independently tested every product and system configuration. Review commands before running them.