Now yes, it's a valid argument to say that it no longer ought to be necessary since iOS and Macs with Apple Silicon are on the same architecture, so the simulator ought to just be like an iOS VM or something like that. You always needed to build separately for the simulator vs real iOS. So we have an 圆4 simulator build for an ARM64 app that is then translated to ARM64 the native architecture of the device being emulated. Do not exclude arm64 for any other SDK.Įxcluding ARM64 from the simulator build will use Rosetta to run the 圆4 simulator. If an update isn’t available from the vendor, temporarily use the EXCLUDED_ARCHS build setting to exclude arm64 for the simulator SDK as shown in the figure below.

Update pre-compiled libraries from vendors If the library producing the build error is a pre-compiled library from a vendor and you don’t have the source code, contact the vendor for an updated XCFramework supporting Apple silicon. Why can't the Simulator just run the native iOS build? Why do I need two ARM64 builds, one for the simulator and one for an iOS device. So I can have an app that will build and run on an M1 iPad and on the iPad simulator on an Intel Mac and also run directly on an M1 Mac (targeting the Mac instead of the emulator) but not on the simulator on an M1 Mac. Combining architectures for iOS, watchOS, or tvOS and their respective simulators into a single binary file is not supported.

Click to expand.From the documentation:Ī pre-compiled library must be built as an XCFramework to separate the device and simulator builds.

Ios emulator mac m1