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

I'm working on an app that includes some Metal code, when building for the simulator we stub out the parts that need Metal using #if targetEnvironment(simulator), which works fine by itself However, the simulator build still fails on trying to compile the .metal file itself, as there is no metal compiler for the simulator. Since there is no need to compile the Metal file for the simulator, I would like to remove the .metal file from the build in case we're building for the simulator, so we can test the rest of the app on the simulator using stubs for our metal code. Is there a way to exclude metal files from the build when building for a simulator ?

I have a third party framework I am using in an iPhone / iPad app.It builds and runs fine.I added a new tvOS target.I added the same frameworks to the tvOS target.When I link I get a linker error that the framework is not found.Can someone please explain?

I have a framework target in Xcode 11.x to build a Dynamic framework with statically linking some 3rd party libraries using pod file. platform :ios, '9.0' #use_frameworks! target 'Framework' do pod 'DeviceUtil', '~> 2.0' end Now I have a requirement to build a Static framework, and for this I changed the Mach-O' type to Static Library in 'Framework's' target build settings and able to create Static framework. The generated framework shows all architectures correctly (for architecture i386): (current ar archive random library for all architecutres x8664, armv7 & arm64)._ But the Static framework does not included 3rd party libraries within the Framework binary. How to generate a Static framework using Xcode11.x which includes other 3rd party libs in its binary? Also changing Mach-O type is good enough to generate a Static framework or is there any other way that

I recently had to duplicate my own frameworks to be able to link them from the native watchOS 2 extension, because the platform is different. So for every framework X I have an X-watchos counterpart.Everything works fine in the simulator and when building directly to my devices, and it wasn't until I tried to archive that I got this linking error:(Link to the picture since they don't seem to be showing: http://i.stack.imgur.com/PcvqP.png)I ran `lipo -i` on the built watchOS framework and sure enough, its archs are `arm7` and `arm64` instead of `armv7k`.When I looked further into the built directory I noticed this:(Link to the picture since they don't seem to be showing: http://i.stack.imgur.com/OSmFu.pngBoth versions are symlinks to the same file, and because the have the same product name, they're being overridden. I could make them have different names, but that would make `import`ing them really cumbersome.Is

I have a pretty basic question. When run my code in order to simulate it, the build succeeds. Then, for whatever reason the simulation crashes. I have figured out the error in my code, but from now on i cant get the code to run again without crashing. I know it is not an error in my code because even if i delete all code and enter a few basic lines, the program always crashes. Is there something i have to do or reset when the simulation crashes in order for the program to run again successfully?