We’re running into the same problem. I tried to work around it using PostProcessBuildPlayer but no success. Feel free to send me an email at pim {at} get-wrecked.com. Here are my findings so far:
This issue occurs when you build using Unity Cloud Build with player settings to build for the iOS Simulator.
The issue does not occur when you build for device (not simulator), because it uses armv7 arm64, which the iOS simulator doesn’t.
Building the exact same project on machine (Mac OS X10.11) works fine, all the way through being able to fully use the project on your iOS simulator.
We need to use Unity Cloud Build with a simulator output because we are uploading the result to appetize.io so that our developers without iPhones can test their code on iOS.
Please send me an email so we can address this issue and create a fix. I’m working on a temp fix using PostProcessBuildPlayer but no success so far.
Also, I’ve tried doing it using the xcode manipulation API, but becuase the player is already built (and the file references and libraries set) you can’t just change it to build for the simulator after you exported the player. There are distinct differences between building for the simulator and for device AFAIK (and from trying it over the past few days)
Building for iOS simulator is not something we currently support. It’s been requested by several other developers so it’s something we are discussing but no immediate plans.