Xcode “framework not found” during linking
Find the exact framework and failing target, then check its linked product and build destination before changing search paths.
Find the exact framework and failing target, then check its linked product and build destination before changing search paths.
Try these fixes in order
Read the linker line
Expand the first linker error in the build report. Record the missing framework, target, configuration, and simulator or device destination.
Check target linkage
In Build Phases, confirm the intended framework or package product is linked to this target. Another target having it does not make it available here.
Check the artifact
For a binary XCFramework, inspect its supported platforms and architectures. A device-only binary will not satisfy a simulator build.
Review custom paths
If the framework is produced locally, verify the build dependency and Framework Search Paths point to its actual output. Avoid broad recursive paths.
Interpret what you see
The named framework is absent from Link Binary With Libraries
What it suggests: The importing target has no direct link to the product.
Next check: Add the intended framework or package product to that target, then rebuild.
The framework is linked but only simulator fails
What it suggests: The binary may not contain an iOS Simulator slice.
Next check: Inspect the XCFramework variants and vendor documentation rather than changing unrelated architecture flags.
The framework is built by another target
What it suggests: Build order or search paths may not point to its produced artifact.
Next check: Check target dependencies and the actual output location in the build report.
Why this happens
- The target does not link the framework or cannot find its build product.
- The binary has no compatible slice for the selected destination.
Still not working?
If the link succeeds but the app crashes at launch, check embedding and runpaths instead; that is a separate problem.
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.