Building for iOS Simulator, but the linked and embedded framework ‘XX.framework‘ was built for

xcodebuild determines this based on the -destination option. How do we apply this when a static library is not built with Xcode? I have a static library (in C) built for several architectures, but I haven't found any way to build an xcframework that associates the correct architecture with the simulator. When I try to construct an xcframework just by appending them all: for lib in *.a; do xcodebuild -create-xcframework -library $lib -headers include -output PEQ.xcframework; done the linking product that consumes them throws a warning: ld: warning: ignoring file .../Release-iphonesimulator/PEQ-x8664.a, missing required architecture arm64 ... And cannot find the symbols. I've also tried linking just the x8664 and arm64 versions in a single call: xcodebuild -create-xcframework -library PEQ-arm64.a -headers include -library PEQ-x86_64.a -headers include -output PEQ.xcframework (If I try to include the i386 or armv7 versions, it complains that they represent tw

Hello, To all the people with the ARCHS[@]: unbound variable error after setting the iOS Simulator SDK to arm64 and who can build for a real device (also for Any IOS Device(arm64)) but can't build the Simulator. I solved my problem following the answer from the user called trishcode in this Stack Overflow post: https://stackoverflow.com/questions/63607158/xcode-12-building-for-ios-simulator-but-linking-in-object-file-built-for-ios What you need to do is: Remove what you did earlier, you MUST NOT set the iOS Simulator SDK to arm64, Set the VALIDARCHS variable with an empty value using a User-Defined build setting, you must set this in the project not in the target (in the main project and Pods project if you are using CocoaPods). Clean and build the project with a Simulator selected (I used iPhone 11). The build will fail. After it fails, go to the pr

OK, so I found the issue, at least for me.I have my own framework which is in a workspace alongside the apps that it is used for. When I added the framework to the app, it would link to an absolute path instead of a relative one. So, I fixed the issue by right clicking the embedded binary for the framework and selecting reveal in project navigator (which is the bar on the left). You can also just click the framework on the left (project navigator). Then you'll see the path is absolute. Change this to relative to build and it should embed properly.

Thanks @satcol's sharing. I confirm that linking and embedding XcodeKit framework in the extension target works.

Yes, that sounds about right.I found that if I clear Dynamic Library Install Name in Build settings - which is defined as $(DYLIB_INSTALL_NAME_BASE:standardizepath)/$(EXECUTABLE_PATH), I am able to install and run the app in the simulator, i.e. the app is not crashing when launched from the Springboard as before. It appears to load all the frameworks and it works on both iPhone and Watch simulator.At the same time, I need Dynamic Libarary Install Name as it is defined by default in order to be able to install the frameworks on the iPhone. But I cannot have both at the same time, apparently. I have kind of found a workaround even though it is not so enjoyable to play with the build settings all the time.All the frameworks I am using are my own, built by myself in Xcode, latest beta on everything. I have checked build settings hundreds of times.It is the oposite on the Watch, by the way. I can run and launch the app in the simulators