Note that there are some explanatory texts on larger screens.

plurals
  1. POSetting Version of iOS simulator from Command line
    primarykey
    data
    text
    <p>Context: Running automated scripts using Xcode's UIAutomation with simulators 6.1 and 5.1 Xcode version is 4.6.1</p> <p>Problem: When running a shell script from the Terminal, UIAutomation ALWAYS opens up 6.1, even though i've set the app path to 5.1.</p> <p>I've tried building and running on 5.1, also if i run the test from Instruments, I'm able to choose the target for 5.1 and it works fine. The problem is only when i run it from the command line.</p> <p>I checked the iphonesimulator.plist and the currentSDKRoot points to the 5.1 path, but as soon as the shell script runs, it changes to 6.1. Is there anyway I can force it to use 5.1?</p> <p>After hours of searching (including the most apt one - <a href="https://stackoverflow.com/questions/12836129/launch-a-specific-hardware-version-of-ios-simulator-using-instruments-command-li">Launch a specific Hardware version of iOS simulator using instruments command line utility</a>) , there seems to be no solution to this.</p> <p>There is a way to set the device using defaults write com.apple.iphonesimulator \ "SimulateDevice" '"iPad"' I need something like defaults write com.apple.iphonesimulator \ "Version" '"5.1"' though obviously that doesn't work. </p> <p>Any pointers will be much appreciated. Thank You!</p> <p>EDIT: I was hoping this would be resolved with XCode 5, but I still have the same issue and iOS7 simulator ALWAYS opens up! Btw,is there a way to circumvent this issue - I'm sure there are many out there running multiple simulator versions.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload