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

Have obtained separate frameworks for device and simulator, and I want to integrate those frameworks to achieve the desired functionality. I have included the simulator framework in my carthage framework project. When I am compiling my framework, I am getting the following error building for iOS-armv7 but attempting to link with file built for iOS-arm64 Undefined symbols for architecture armv7: OBJCCLASS$..., referenced from: objc-class-ref in ViewController.o OBJCCLASS$..., referenced from: objc-class-ref in DepedencyInjector.o objc-class-ref in ViewController.o ld: symbol(s) not found for architecture armv7 clang: error: linker command failed with exit code 1 (use -v to see invocation) Can someone please help me resolve this

I'm experimenting with creating a Framework and have noticed a difference when dragging and dropping/or adding it into a project. If I create a brand new app and add the Framework then Xcode automatically creates a Frameworks, Libraries, and Embedded section within the app settings general section. The framework gets added with a default embed setting of Do Not Embed, which can be changed to Embed & Sign or Embed without Signing. However, I have an existing app which doesn't already contain a Frameworks, Libraries, and Embedded section section, if I add the framework to that app then Xcode is NOT creating a Frameworks, Libraries, and Embedded section, instead it is adding the framework to the existing Link Libraries with Binary section. However this section does not have the embed box that a Frameworks, Libraries, and Embedded section has. Why is there this difference? And how can

I want to generate two frameworks: one for iOS and one for Simulator. Are there any differences between them?

Is it possible to generate release build for simulator of a dynamic framework in iOS?

Our iOS apps use to embed and sign third party frameworks built for various architectures (i386 x86_64 armv7 arm64). When building an archive, a script phase strips unwanted architectures (simulator ones) from the build. Everything was working fine until XCode 12.3 (updated this morning). Now, what seems to be a Target integrity check always reports the following error for these embedded frameworks (example with GoogleCast framework): error: Building for iOS, but the linked and embedded framework 'GoogleCast.framework' was built for iOS + iOS Simulator. Also, as these frameworks are synced from a server at build time using a script phase, if I delete the frameworks before compiling, there are no errors and the app is built properly. But if the frameworks are already synced, the compilation systematically f

I am trying to build the a project which uses a third party framwork written in Objective C. My tvOS project is written completely in swift. I am getting more than 100 similar warning messages. Also, I have cocoa pods installed.Does anyone faced the similar issue? Please help to resolve these warning messages.

While trying to get a System Extension version of our VPN client working I realized that the system extensions aren't actually run from their location in the application bundle `<myapp>.app/Contents/Library/SystemExtensions/<myextension>` but are rather copied to `/Library/SystemExtensions/<GUID>/<myextension>`Which is all well and good but it means the running system extension cannot access the frameworks embedded in the application bundle using any @rpath configuration I can think of. Technically it would be possible to hardcode `/Applications/<myapp>.app/...` since by Apple's decree SystemExtensions are only expected to work when contained by applications installed in `/Applications` but that won't fly while doing development.Am I doomed to double embed all the common needed internal frameworks inside both my app and the System Extension or is there some way to set up @rpath which will let the System Extension access my app's embedded frameworks