![]() Xcode is going through a lot of rapid improvements in the beta phase, so there is probably going to be some unexpected behaviour. If none of the 7 suggestions work then I would recommend you raise a bug ticket on Feedback Assistant. It would also be a good idea to restart Xcode between attempts. The legacy build system is deprecated, and will be removed in a futureįor each of these steps, make sure you clear Derived Data and rebuild. Conflicting settings here could be the issue. Also, I would check if you are using the new Build System for your build settings for Pods and app targets.This works as a workaround for many build/runtime bugs in Xcode. ![]() Disable these scheme settings (in Edit Scheme in the toolbar), as well as Main Thread Checker.It's strange that you are using the arm architecture - usually simulator builds are x86_64, hence you need to address any conflicting architecture build settings (are you using Mac Catalyst or the Developer Transition Kit perhaps?). Ĭheck your Architecture Build Settings are set to $(ARCHS_STANDARD) for all targets. Make sure you've got simulator device support files in here.Īlso if you have previous Xcode betas installed, make sure you set the Command Line Tools again to the latest Xcode beta you want to use (they get deactivated if you install a new version of Xcode).Īs mentioned in other answers, remove the $(VALID_ARCHS) build setting from your main and CocoaPods targets. Worth checking the contents of Contents -> Developer -> Platforms -> atform -> DeviceSupport for iOS 9. ![]() ![]() Xcode now supports debugging apps and running tests on The Swift project uses one set of keys for snapshot builds, and separate keys for every official release. However, building for device supports iOS 9 and above: When running in macOS 11, Simulator supports iOS 11.4 or later.
0 Comments
Leave a Reply. |