I have an Xcode workspace which features a project with an iOS Application target, and another project with a Framework target. The framework target is dependent on another framework, which is integrated in the form of an xcframework
:
Using regular OtherFramework.framework
would require it to be linked to MyFramework
and then embedded in MyApp
even though MyApp
doesn't require the framework itself. However when integrating with xcframework
, this project then fails to build with a No such module 'OtherFramework'
error.
Project settings:
MyFramework Project
MyApp Project
Removing OtherFramework.xcframework
from the MyApp
target fixes the build issue, but then causes library not loaded
errors as the framework is not present in the application.
Demo project here: https://github.com/msaps/XCFramework-Link-Issue
How are you meant to link an xcframework
in an application and link in a dependent framework?
pyckamil just posted this article which explains the issue in detail: Everything wrong with XCFrameworks.
It turns out Xcode has an optimisation for the ProcessXCFrameworkLibrary
step which extracts the correct .framework
from an .xcframework
for the active build architecture. This is only run once which causes issues for additional targets that try to link the same framework.
This issue is resolved in Xcode 12.0
UPDATED - Resolved in Xcode 12.0
shinsuk came up with a reliable workaround that works by adding architecture-explicit framework search paths to ensure the correct .framework
within an XCFramework is found.
Details can be found in the README.
Check build settings and defining the Framework Search Paths to a folder which contains the frameworks in question. If the frameworks are placed in your project directory, simply set the framework search path to $(SRCROOT) and set it to recursive.
check the response Getting error "No such module" using Xcode, but the framework is there
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With