New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Xcode 7/iOS 9Could not find a device to launch. You requested 'iPhone 6 (9.0 Simulator)' #5624
Comments
Can you provide the full Appium server log? The code looks right for getting the desired string from xcode 7. if (opts.iOSSDKVersion >= 8 && xcodeMajorVer === 7) {
iosDeviceString += " (" + reqVersion + ")";
} |
@skycamefalling what device are you trying? |
This is what I get when the test fails:
|
This is my appium.txt file
I have only tried simulators. I have tried to change the names to the ones that are shown in the error messages. |
+1 seeing same issue on latest Appium and Xcode 7 |
+1 I also see this issue on appium 1.4.11 and Xcode 7 |
Also, I am on OS X 10.10.5 if that makes any difference. |
Think this should be fixed in the next release - |
I met the same problem. Currently i am using appium 1.4.8 on MAC. For details ,please refer screenshot.
|
iOS 9 is not supported in 1.4.8. The minimum version is 1.4.9. This particular issue will be fixed in the next release, which is immanent. |
Will that be an update to 1.5? i have beta4 and I still get the same error. |
@imurchie Thanks, i am going to update to 1.4.9 on MAC |
@SouWilliams i had similar problem running with iPhone 6 even after updating appium to 1.4.11 . npm install -g appium@1.4.11 will update the appium server. Just change the deviceName to iPhone 6s ... this would work for u .. |
@saikrishna321 Thanks for your solution. But i still got the same error. The code has been changed to below:
For the errors, please refer screenshot. Hope can get some help. |
@SouWilliams i just ran my test locally i was successful in running in iPhone 6S. can you try the below code ... public class IOSWebTest {
|
@saikrishna321 Thanks, but it's not working on my machine... |
Hi Guys, i have solved this issue. Just upgrade to the latest version(1.4.11). This time i try to use npm to install appium, it's working. But when i start appium in the command line by use "appium &" i have no idea how to shut it down. Do you have any ideas on how to shutdown appium in command line ? |
@SouWilliams killall -9 node should help |
@saikrishna321 Many thanks! |
I have this problem after updating of appium to the latest beta v1.5.0-beta4 today. I use node v0.12.7.
I think this "Final device string is: 'iPhone (9.0 Simulator)'" has already fixed in beta v1.5.0-beta4 but this error is displayed. |
Tried to download appium source code from github and run reset.sh script as suggested on this link - https://discuss.appium.io/t/new-xcode-breaks-ios-emulator-initiation/6051. When can we expect a new release with the fix please ? Right now appium.io has 1.4.8 dmg when downloaded. My team uses the .dmg file as server and generally doesn't update node or any other underlying binaries, so really appreciate if we have the dmg. Thanks |
The |
@SouWilliams the Google |
That's really help . Thanks @marrs |
+1 seeing same issue on latest Appium and Xcode 7 |
+1 for non-9.0 on Mac; seems more like a general disconnect between XCode simulator and Appium request. XCode 7.0.1
|
@kiminoa , i suggest to update to 1.4.13. On this version, it works on my laptop. |
@SouWilliams, can you help me with appium version 1.4.13.
|
Up and running using "appium &" (1.4.13) instead of Appium GUI. |
Any fix for the the GUI? |
I am seeing this on 1.4.16 as well. Can someone please help? |
Can someone please help? |
I haven't tried 1.4.16, but did you install the needed simulators? On 1.4.13 there was some issue with simulator. I got around it by running the following steps. Not sure if this will help you. I can't think of anything else. |
I should have mentioned that i am trying on real device not on simulator. sorry about that. |
@scottdixon This has been fixed in Appium 1.5 and it works fine as expected.Please close this. |
This should be resolved in recent versions of Appium. Reopen if any issues. |
where can I find Appium 1.5? I'm experiencing issues with Appium 1.4.13 and iPhone 6 simulator |
From |
I just ran
Ending your web drivage..
` appium node module is 1.5.1 but Appium.app is on 1.4.13 |
Your appium-version is still at 1.3 - try changing that to 1.5 On Thu, Mar 31, 2016 at 2:23 PM, Sze Chan notifications@github.com wrote:
|
How do I change the appium version? I couldn't find any docs saying how to change appium version. thanks! |
Change it where ever you have this code. Looks like your caps file. |
I'm still new to appium, where is caps file? |
I found out where to make the changes thanks everyone! |
No problem! |
Facing the same issue on Appium 1.4.15 and 1.4.13 Command used for running Any suggestions? |
Can you provide the full server logs as a gist |
Logs can be found here https://gist.github.com/eagle19/600488d68dae0d513433a76088f0cfb4#file-logs-txt |
Sorry. By full I mean from the session start to when it fails. So we can see the desired capabilities, etc., and the steps the server is taking. |
@eagle19 You need to either create an |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
This happened on 1.4.11 and 1.5.0beta4
It looks like the values are hardcoded into the code. This is causing appium with the ruby bindings to not be able to find the device. It looks as if in Xcode 7 they changed the device names - as you can see not one of them has simulator in the name.
["iPhone (5) (8.3) [9a344d3d575e223dff41bdc02bd678c71b7b14d2]","iPad 2 (8.4) [AF764A2F-5726-4C45-BE16-61FF3F4619E3]","iPad 2 (9.0) [833D62D8-FB33-4C2D-B7CC-637A35E3EDC0]","iPad Air (8.4) [DE706051-ECDB-4E27-9559-ED0A5D57C3B6]","iPad Air (9.0) [692C92DC-A6D9-4FF9-9A7A-8E21689E25F8]","iPad Air 2 (9.0) [A7475C30-2B9C-451B-8E48-AD18A4A83C55]","iPad Retina (8.4) [EB8D8454-07B9-4D0C-A09A-4FB2D29F28E8]","iPad Retina (9.0) [FE5BCE7B-34CF-4213-9B2B-36AADB575361]","iPhone 4s (8.4) [F818F47D-2FA1-4C96-A031-3A488EBF4BD5]","iPhone 4s (9.0) [F37442CD-2961-41CD-A01B-8031A3F075B7]","iPhone 5 (8.4) [5035576B-A6B0-4230-8BDD-472F5AD5907D]","iPhone 5 (9.0) [4A93F6ED-4B0E-4D39-BEDB-61EC4AF5A249]","iPhone 5s (8.4) [9D3400BD-936C-4988-AE9A-912C5A3DBBCF]","iPhone 5s (9.0) [59042C9B-E299-4DA3-9F5B-43E16B0E2BDB]","iPhone 6 (8.4) [F56899F3-AC46-4187-A84F-A95C88B14698]","iPhone 6 (9.0) [C76BF3AB-1D44-40B3-914A-F31B3EFF8636]","iPhone 6 (9.0) + Apple Watch - 38mm (2.0) [CB508F71-C277-4F0A-954D-0ED837240789]","iPhone 6 Plus (8.4) [04FB146F-2C33-4A1E-89E8-F51E52FFD2EC]","iPhone 6 Plus (9.0) [9429AF68-A830-4EB6-BB82-E5E6D001D741]","iPhone 6 Plus (9.0) + Apple Watch - 42mm (2.0) [E82BACA6-052A-4007-83A9-F888729BAF85]","iPhone 6s (9.0) [664811ED-CB14-4D16-BA95-640B2BC5456A]","iPhone 6s Plus (9.0) [03108BB5-9CE5-4627-9718-262B95C353A8]"]
See ios.js line 998 - 1037
The text was updated successfully, but these errors were encountered: