Can’t get menu "iPhone Retina (3.5-inch)"
Closed this issue · 8 comments
Hi !
I'm running
./run_screenshooter.sh ~/Desktop/screenshots
And I get this error :
bin/choose_sim_device:2036:2041: execution error: System Events got an error: Can’t get menu "iPhone Retina (3.5-inch)" of menu item "iPhone Retina (3.5-inch)" of menu 1 of menu item 1 of menu 1 of menu bar item 5 of menu bar 1 of process "iOS Simulator". (-1728)
Here is the full gist of what is happening : https://gist.github.com/Palleas/67a99c500d589e6ea643
Any idea why ?
I'm running Xcode 5 with OSX 10.9.
Thanks !
Hmm. Can you take a screen shot of the "Hardware" menu in your simulator? The bin/choose_sim_device
script uses Apple Script to drill down into that menu to choose a simulator device version. It can't seem to find it on your Mac.
Hmm. Do you have the latest code from the master branch? It looks like your menu items match the script. I just double checked with my copy of Xcode 5 and everything worked fine over here. 2 months ago this commit addressed the problem you are describing. I'd fetch the latest on master and see if it resolves.
I'm having the same issue and I've pulled the latest Master. Any other thoughts on this issue:
** BUILD SUCCEEDED **
bin/choose_sim_device:2036:2041: execution error: System Events got an error: Can’t get menu "iPhone Retina (3.5-inch)" of menu item "iPhone Retina (3.5-inch)" of menu 1 of menu item 1 of menu 1 of menu bar item 5 of menu bar 1 of process "iOS Simulator". (-1728)
@Kotai what version of Xcode and OS X are you running? I'm not able to reproduce this error so I'm at a loss on how to fix it. My best guess at this point is it's a configuration error on your machines or you have older bits of Xcode lying around. Can you share a screen shot of your iOS hardware menu?
AHA! I found it @Kotai and @Palleas. The problem is that the choosing script needed to be flexible enough to work on systems that don't have older iOS SDKs installed. I have iOS 6.1 installed so there's an extra submenu in there to choose beneath the device family. I pushed up a new change that fixed the problem in my tests for both configurations.
If it still isn't working reopen the issue and we'll try again.
Brilliant! Works now, thanks!