EDIT Jan 16 2017: We no longer recommend using UUIDs to start simulators. The OS X image has been updated to resolve the underlying issue, and using UUIDs is no longer necessary. Please check out this post for examples of how to choose the simulators by name.
Hey,
please rather use a simulator UUID than a name. I can’t explain why but sometimes they don’t work as well.
This should start and build your app with the iOS 9.3 iPhone 6 simulator:
set -o pipefail && xcodebuild -workspace 'pop_app_ios.xcworkspace' -scheme 'pop_app_ios' clean build test -sdk iphonesimulator -destination 'id=547B1B63-3F66-4E5B-8001-F78F2F1CDEA7' CODE_SIGNING_REQUIRED=NO CODE_SIGN_IDENTITY= PROVISIONING_PROFILE= | tee $CIRCLE_ARTIFACTS/xcode_raw.log | xcpretty --color --report junit --output $CIRCLE_TEST_REPORTS/xcode/results.xml
@anon47539524 Thanks for your reply. Is there someway to get the list of Simulator UUIDs ? How to know the specs of the simulator for the UUID that you provided ?
/cc @drazisil
You can also get a list of all the simulators installed with either xcrun instruments -s or with xcrun simctl list.
Please note that these UUIDs for the simulators are different for every Xcode install (UUID=Unique Universal Identifier). I will update the docs over the week to properly list all simulators UUIDs available to you. From iOS 8.4 to 10.0.
Hello William,
Below is the circle.yml that I am using successfully now.
Replace the -workspace and -scheme values with the appropriate values from your app.