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

iOS 10 support #6597

Closed
romainlouvet opened this Issue Jun 17, 2016 · 101 comments

Comments

Projects
None yet
@romainlouvet

romainlouvet commented Jun 17, 2016

The problem

Appium can't launch ipa with iOS 10 beta / Xcode 8 beta.

[MJSONWP] Encountered internal error running command: Error: Could not find Automation.tracetemplate in any of the followinglocations /Applications/Xcode-beta.app/Contents/Applications/Instruments.app/Contents/PlugIns/AutomationInstrument.xrplugin/Contents/Resources/Automation.tracetemplate,/Applications/Xcode-beta.app/Contents/Applications/Instruments.app/Contents/PlugIns/AutomationInstrument.bundle/Contents/Resources/Automation.tracetemplate
at getAutomationTraceTemplatePathWithoutRetry$ (lib/xcode.js:172:9)

Environment

  • Appium version : 1.5.3
  • Desktop OS/version used to run Appium: OS X 10.11.5
  • Mobile platform/version under test: iPhone 5SE with iOS 10
  • Real device or emulator/simulator: Real device
    Xcode 8 beta

Link to Appium logs

https://gist.github.com/romainlouvet/098e33195ea8be2989bb0fc82e270af2

@triager triager added the NeedsTriage label Jun 17, 2016

@imurchie

This comment has been minimized.

Show comment
Hide comment
@imurchie

imurchie Jun 20, 2016

Member

Did this ipa install with Xcode 7? The installation doesn't seem to be a problem locally.

On the other hand, Xcode 8 beta does not include any automation trace template for Instruments, so it won't work with Appium at the moment. We are looking into how to get around this at the moment (any help would be appreciated).

Member

imurchie commented Jun 20, 2016

Did this ipa install with Xcode 7? The installation doesn't seem to be a problem locally.

On the other hand, Xcode 8 beta does not include any automation trace template for Instruments, so it won't work with Appium at the moment. We are looking into how to get around this at the moment (any help would be appreciated).

@romainlouvet

This comment has been minimized.

Show comment
Hide comment
@romainlouvet

romainlouvet Jun 21, 2016

it's not possible to install ipa with xcode 7 / ios 10

romainlouvet commented Jun 21, 2016

it's not possible to install ipa with xcode 7 / ios 10

@imurchie

This comment has been minimized.

Show comment
Hide comment
@imurchie

imurchie Jun 21, 2016

Member

What are the logs for that situation?

Member

imurchie commented Jun 21, 2016

What are the logs for that situation?

@romainlouvet

This comment has been minimized.

Show comment
Hide comment
@romainlouvet

romainlouvet Jun 22, 2016

Xcode 7.3.1 / Build version 7D1014
iPhone 5SE iOS 10 Beta

https://gist.github.com/romainlouvet/3f99397137b6b396277003a740ea984b

romainlouvet commented Jun 22, 2016

Xcode 7.3.1 / Build version 7D1014
iPhone 5SE iOS 10 Beta

https://gist.github.com/romainlouvet/3f99397137b6b396277003a740ea984b

@romainlouvet

This comment has been minimized.

Show comment
Hide comment
@romainlouvet

romainlouvet Jun 22, 2016

If I try to manipulate my device(iOS 10) with idevicediagnostics

idevicediagnostics restart
-> ERROR: Could not connect to lockdownd, error code -5

romainlouvet commented Jun 22, 2016

If I try to manipulate my device(iOS 10) with idevicediagnostics

idevicediagnostics restart
-> ERROR: Could not connect to lockdownd, error code -5

@meirtsvi

This comment has been minimized.

Show comment
Hide comment
@meirtsvi

meirtsvi Jun 22, 2016

Compile libimobiledevice from the latest code and you're all set up:
libimobiledevice/libimobiledevice#327

meirtsvi commented Jun 22, 2016

Compile libimobiledevice from the latest code and you're all set up:
libimobiledevice/libimobiledevice#327

@imurchie

This comment has been minimized.

Show comment
Hide comment
@imurchie

imurchie Jun 22, 2016

Member

That will allow you to install the app.

The fact remains that Apple dropped Instruments support in Xcode 8, and Appium uses Instruments to automate the device.

Member

imurchie commented Jun 22, 2016

That will allow you to install the app.

The fact remains that Apple dropped Instruments support in Xcode 8, and Appium uses Instruments to automate the device.

@romainlouvet

This comment has been minimized.

Show comment
Hide comment
@imurchie

This comment has been minimized.

Show comment
Hide comment
@imurchie

imurchie Jun 22, 2016

Member

We are actively working on an XCUITest driver to integrate into Appium. It's not quite ready for prime time, though.

Member

imurchie commented Jun 22, 2016

We are actively working on an XCUITest driver to integrate into Appium. It's not quite ready for prime time, though.

@skumar1122

This comment has been minimized.

Show comment
Hide comment
@skumar1122

skumar1122 Jul 25, 2016

Hello imurchie ,

I wanted to run automation -selenium-java scripts on new iOS 10.0 with Xcode 8 ..While I run IWDP I can see these error :
ss.add_fd(3)
ss.recv fd=3 len=294
ss.recv fd=3 len=682
ss.add_server_fd(4)
Could not connect to lockdownd. Exiting.: Permission denied
ss.remove_server_fd(4)
Unable to attach 9285c264a00455134d31e698ed542463bdaff43c inspector

wanted to find out can we not use xcode8 beta with Appium 1.5.3 ?

thanks
Shiva

skumar1122 commented Jul 25, 2016

Hello imurchie ,

I wanted to run automation -selenium-java scripts on new iOS 10.0 with Xcode 8 ..While I run IWDP I can see these error :
ss.add_fd(3)
ss.recv fd=3 len=294
ss.recv fd=3 len=682
ss.add_server_fd(4)
Could not connect to lockdownd. Exiting.: Permission denied
ss.remove_server_fd(4)
Unable to attach 9285c264a00455134d31e698ed542463bdaff43c inspector

wanted to find out can we not use xcode8 beta with Appium 1.5.3 ?

thanks
Shiva

@VTINFOJames

This comment has been minimized.

Show comment
Hide comment
@VTINFOJames

VTINFOJames Jul 29, 2016

I've tried xCode 8 beta 3 with Appium 1.5.3 not knowing about the deprecation of UIAutomation in xCode. The obvious outcome is that Appium is unable to launch the application.

VTINFOJames commented Jul 29, 2016

I've tried xCode 8 beta 3 with Appium 1.5.3 not knowing about the deprecation of UIAutomation in xCode. The obvious outcome is that Appium is unable to launch the application.

@imurchie

This comment has been minimized.

Show comment
Hide comment
@imurchie

imurchie Jul 29, 2016

Member

Yes, unfortunately.

There is good news, though. We are working hard on getting XCUITest supported. At the moment much of it works, but there are things to iron out. If you would like to try, you need to use Appium from its source.

We would love to have more people trying it out, though it is definitely a work in progress.

Member

imurchie commented Jul 29, 2016

Yes, unfortunately.

There is good news, though. We are working hard on getting XCUITest supported. At the moment much of it works, but there are things to iron out. If you would like to try, you need to use Appium from its source.

We would love to have more people trying it out, though it is definitely a work in progress.

@ericwengelking

This comment has been minimized.

Show comment
Hide comment
@ericwengelking

ericwengelking Jul 29, 2016

For the record Appium does work with Xcode 8 beta 3 if you are using appium-xcuitest-driver by building Appium from source

ericwengelking commented Jul 29, 2016

For the record Appium does work with Xcode 8 beta 3 if you are using appium-xcuitest-driver by building Appium from source

@meirtsvi

This comment has been minimized.

Show comment
Hide comment
@meirtsvi

meirtsvi Jul 30, 2016

From what I've read in the source code there is no support for running apps on real device, right?

meirtsvi commented Jul 30, 2016

From what I've read in the source code there is no support for running apps on real device, right?

@imurchie

This comment has been minimized.

Show comment
Hide comment
@imurchie

imurchie Jul 30, 2016

Member

Running from source gives you all the capabilities that are the releases,
plus new development since the last release.

On Friday, July 29, 2016, Meir Tsvi notifications@github.com wrote:

From what I've read in the source code there is no support for running
apps on real device, right?


You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#6597 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/ACfkUvptn89AkCpLrqV7nEknaav0Lueoks5qauQ-gaJpZM4I4Kkc
.

Member

imurchie commented Jul 30, 2016

Running from source gives you all the capabilities that are the releases,
plus new development since the last release.

On Friday, July 29, 2016, Meir Tsvi notifications@github.com wrote:

From what I've read in the source code there is no support for running
apps on real device, right?


You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#6597 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/ACfkUvptn89AkCpLrqV7nEknaav0Lueoks5qauQ-gaJpZM4I4Kkc
.

@meirtsvi

This comment has been minimized.

Show comment
Hide comment
@meirtsvi

meirtsvi Jul 30, 2016

Specifically for xcui driver, there is no support for running on real device yet. Here is a pr that was not yet integrated: appium/appium-xcuitest-driver#69
I'm I missing something?

meirtsvi commented Jul 30, 2016

Specifically for xcui driver, there is no support for running on real device yet. Here is a pr that was not yet integrated: appium/appium-xcuitest-driver#69
I'm I missing something?

@imurchie

This comment has been minimized.

Show comment
Hide comment
@imurchie

imurchie Jul 30, 2016

Member

Yes, for xxuitest real device support is waiting on that pr. It ought to be
merged early on Monday.

On Friday, July 29, 2016, Meir Tsvi notifications@github.com wrote:

Specifically for xcui driver, there is no support for running on real
device yet. Here is a pr that was not yet integrated:
appium/appium-xcuitest-driver#69
appium/appium-xcuitest-driver#69
I'm I missing something?


You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#6597 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/ACfkUtLusMwR9MkcwKru7qVxOur3VKfFks5qaukugaJpZM4I4Kkc
.

Member

imurchie commented Jul 30, 2016

Yes, for xxuitest real device support is waiting on that pr. It ought to be
merged early on Monday.

On Friday, July 29, 2016, Meir Tsvi notifications@github.com wrote:

Specifically for xcui driver, there is no support for running on real
device yet. Here is a pr that was not yet integrated:
appium/appium-xcuitest-driver#69
appium/appium-xcuitest-driver#69
I'm I missing something?


You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#6597 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/ACfkUtLusMwR9MkcwKru7qVxOur3VKfFks5qaukugaJpZM4I4Kkc
.

@JaniJegoroff

This comment has been minimized.

Show comment
Hide comment
@JaniJegoroff

JaniJegoroff Jul 30, 2016

Member

@imurchie I'm trying to run Appium Ruby bindings tests against the latest code but I get stuck to [XCUITest] Launching WebDriverAgent on the device phase. Any tips how to proceed from there?

Janis-iMac:appium janijegoroff$ node .
[Appium] Welcome to Appium v1.5.3 (REV 068c4e5d0a7683956fb03c8ba81026106f016da7)
[Appium] Appium REST http interface listener started on 0.0.0.0:4723
[HTTP] --> POST /wd/hub/session {"desiredCapabilities":{"platformName":"iOS","platformVersion":"10.0","deviceName":"iPhone 6","app":"/Users/janijegoroff/projects/ruby_lib/ios_tests/UICatalog.app","automationName":"XCUITest"}}
[MJSONWP] Calling AppiumDriver.createSession() with args: [{"platformName":"iOS","pla...
[Appium] Creating new XCUITestDriver session
[Appium] Capabilities:
[Appium]   platformName: 'iOS'
[Appium]   platformVersion: '10.0'
[Appium]   deviceName: 'iPhone 6'
[Appium]   app: '/Users/janijegoroff/projects/ruby_lib/ios_tests/UICatalog.app'
[Appium]   automationName: 'XCUITest'
[BaseDriver] Session created with session id: 35062c79-a8bd-43dc-a149-699354e9bb3f
[iOSSim] Constructing iOS simulator for Xcode version 8.0 with udid '2CD5B95B-C8D4-42CB-BCC0-FF78C6C5F851'
[XCUITest] Determining device to run tests on: udid: '2CD5B95B-C8D4-42CB-BCC0-FF78C6C5F851', real device: false
[debug] [XCUITest] Checking whether app is actually present
[debug] [ios-app-utils] Getting bundle ID from app
[XCUITest] Setting up simulator
[XCUITest] Simulator with udid '2CD5B95B-C8D4-42CB-BCC0-FF78C6C5F851' not booted. Booting up now
[debug] [iOSSim] Killing all iOS Simulators
[iOSSim] Starting simulator with command: open /Applications/Xcode-beta.app/Contents/Developer/Applications/Simulator.app --args -CurrentDeviceUDID 2CD5B95B-C8D4-42CB-BCC0-FF78C6C5F851
[iOSSim] No boot indicator case for platform version '10.0'
[iOSSim] Tailing simulator logs until we encounter the string "no boot indicator string available"
[iOSSim] We will time out after 60000ms
[debug] [iOSSim] Simulator startup timed out. Continuing anyway.
[debug] [iOSSim] Waiting an extra 2000ms for the simulator to really finish booting
[debug] [iOSSim] Done waiting extra time for simulator
[iOSSim] Simulator booted in 62125ms
[XCUITest] Using default agent: /Users/janijegoroff/projects/appium/node_modules/appium-xcuitest-driver/WebDriverAgent/WebDriverAgent.xcodeproj
[XCUITest] Using default bootstrap: /Users/janijegoroff/projects/appium/node_modules/appium-xcuitest-driver/WebDriverAgent
[XCUITest] Launching WebDriverAgent on the device
Member

JaniJegoroff commented Jul 30, 2016

@imurchie I'm trying to run Appium Ruby bindings tests against the latest code but I get stuck to [XCUITest] Launching WebDriverAgent on the device phase. Any tips how to proceed from there?

Janis-iMac:appium janijegoroff$ node .
[Appium] Welcome to Appium v1.5.3 (REV 068c4e5d0a7683956fb03c8ba81026106f016da7)
[Appium] Appium REST http interface listener started on 0.0.0.0:4723
[HTTP] --> POST /wd/hub/session {"desiredCapabilities":{"platformName":"iOS","platformVersion":"10.0","deviceName":"iPhone 6","app":"/Users/janijegoroff/projects/ruby_lib/ios_tests/UICatalog.app","automationName":"XCUITest"}}
[MJSONWP] Calling AppiumDriver.createSession() with args: [{"platformName":"iOS","pla...
[Appium] Creating new XCUITestDriver session
[Appium] Capabilities:
[Appium]   platformName: 'iOS'
[Appium]   platformVersion: '10.0'
[Appium]   deviceName: 'iPhone 6'
[Appium]   app: '/Users/janijegoroff/projects/ruby_lib/ios_tests/UICatalog.app'
[Appium]   automationName: 'XCUITest'
[BaseDriver] Session created with session id: 35062c79-a8bd-43dc-a149-699354e9bb3f
[iOSSim] Constructing iOS simulator for Xcode version 8.0 with udid '2CD5B95B-C8D4-42CB-BCC0-FF78C6C5F851'
[XCUITest] Determining device to run tests on: udid: '2CD5B95B-C8D4-42CB-BCC0-FF78C6C5F851', real device: false
[debug] [XCUITest] Checking whether app is actually present
[debug] [ios-app-utils] Getting bundle ID from app
[XCUITest] Setting up simulator
[XCUITest] Simulator with udid '2CD5B95B-C8D4-42CB-BCC0-FF78C6C5F851' not booted. Booting up now
[debug] [iOSSim] Killing all iOS Simulators
[iOSSim] Starting simulator with command: open /Applications/Xcode-beta.app/Contents/Developer/Applications/Simulator.app --args -CurrentDeviceUDID 2CD5B95B-C8D4-42CB-BCC0-FF78C6C5F851
[iOSSim] No boot indicator case for platform version '10.0'
[iOSSim] Tailing simulator logs until we encounter the string "no boot indicator string available"
[iOSSim] We will time out after 60000ms
[debug] [iOSSim] Simulator startup timed out. Continuing anyway.
[debug] [iOSSim] Waiting an extra 2000ms for the simulator to really finish booting
[debug] [iOSSim] Done waiting extra time for simulator
[iOSSim] Simulator booted in 62125ms
[XCUITest] Using default agent: /Users/janijegoroff/projects/appium/node_modules/appium-xcuitest-driver/WebDriverAgent/WebDriverAgent.xcodeproj
[XCUITest] Using default bootstrap: /Users/janijegoroff/projects/appium/node_modules/appium-xcuitest-driver/WebDriverAgent
[XCUITest] Launching WebDriverAgent on the device
@imurchie

This comment has been minimized.

Show comment
Hide comment
@imurchie

imurchie Aug 1, 2016

Member

It seems the system log location for the newest beta of Xcode 8 moved, so Appium was not able to find the information it needed. Fixing.

There is also the issue that the boot indicator has changed, and I'm not able to find anything that seems reasonable to wait for. So, as is seen in the logs above, Appium waits 60s for the simulator to boot, even though it boots much more quickly than that usually.

If anyone wanted to dig into the logs a little bit, to see if there is anything that reliably comes up to indicate that the sim is actually booted, it would be much appreciated!

The indicators for previous versions are found here: https://github.com/appium/appium-ios-simulator/blob/master/lib/simulator-xcode-6.js#L189-L211

Member

imurchie commented Aug 1, 2016

It seems the system log location for the newest beta of Xcode 8 moved, so Appium was not able to find the information it needed. Fixing.

There is also the issue that the boot indicator has changed, and I'm not able to find anything that seems reasonable to wait for. So, as is seen in the logs above, Appium waits 60s for the simulator to boot, even though it boots much more quickly than that usually.

If anyone wanted to dig into the logs a little bit, to see if there is anything that reliably comes up to indicate that the sim is actually booted, it would be much appreciated!

The indicators for previous versions are found here: https://github.com/appium/appium-ios-simulator/blob/master/lib/simulator-xcode-6.js#L189-L211

@skumar1122

This comment has been minimized.

Show comment
Hide comment
@skumar1122

skumar1122 Aug 1, 2016

so now Will it work from NPM install or still need to use through source code ?

skumar1122 commented Aug 1, 2016

so now Will it work from NPM install or still need to use through source code ?

@imurchie

This comment has been minimized.

Show comment
Hide comment
@imurchie

imurchie Aug 1, 2016

Member

It is still only available through the source, and it is still a work in progress.

Member

imurchie commented Aug 1, 2016

It is still only available through the source, and it is still a work in progress.

@skumar1122

This comment has been minimized.

Show comment
Hide comment
@skumar1122

skumar1122 Aug 1, 2016

awesome ! thank you

skumar1122 commented Aug 1, 2016

awesome ! thank you

@rafalf

This comment has been minimized.

Show comment
Hide comment
@rafalf

rafalf Aug 7, 2016

I presume that python client will have to be rewritten for xcui? any predictions when will that be all integrated altogether in appium? i am about to start using this tool but uiautomation aint supported by apple any longer i recon i must wait for xcui

rafalf commented Aug 7, 2016

I presume that python client will have to be rewritten for xcui? any predictions when will that be all integrated altogether in appium? i am about to start using this tool but uiautomation aint supported by apple any longer i recon i must wait for xcui

@imurchie

This comment has been minimized.

Show comment
Hide comment
@imurchie

imurchie Aug 7, 2016

Member

Unfortunately, I am the main one working on implementing the XCUITest integration and the main one who takes care of the Python client, so it will be slow.

For the most part there will be no changes, other than sending direct UI Automation commands for finding elements.

Member

imurchie commented Aug 7, 2016

Unfortunately, I am the main one working on implementing the XCUITest integration and the main one who takes care of the Python client, so it will be slow.

For the most part there will be no changes, other than sending direct UI Automation commands for finding elements.

@Nesaganesh

This comment has been minimized.

Show comment
Hide comment
@Nesaganesh

Nesaganesh Aug 8, 2016

imurchie Do you have any idea when are you planning to complete this, are you anytime closer to the completion, sorry to trouble you, just wanted to know in curiosity

Nesaganesh commented Aug 8, 2016

imurchie Do you have any idea when are you planning to complete this, are you anytime closer to the completion, sorry to trouble you, just wanted to know in curiosity

@ghost

This comment has been minimized.

Show comment
Hide comment
@ghost

ghost Aug 22, 2016

@imurchie, Please update if the latest work on appium-xcuitest-driver supports testing on iOS 10 real devices. from "appium/appium-xcuitest-driver#69", It only creates session and no other functionalities are supported.

ghost commented Aug 22, 2016

@imurchie, Please update if the latest work on appium-xcuitest-driver supports testing on iOS 10 real devices. from "appium/appium-xcuitest-driver#69", It only creates session and no other functionalities are supported.

@imurchie

This comment has been minimized.

Show comment
Hide comment
@imurchie

imurchie Aug 22, 2016

Member

I don't understand your question.

Member

imurchie commented Aug 22, 2016

I don't understand your question.

@ghost

This comment has been minimized.

Show comment
Hide comment
@ghost

ghost Aug 22, 2016

Would like know, if the latest changes on appium supports testing all functionality on iOS 10 real devices.

ghost commented Aug 22, 2016

Would like know, if the latest changes on appium supports testing all functionality on iOS 10 real devices.

@pavanbachu0604

This comment has been minimized.

Show comment
Hide comment
@pavanbachu0604

pavanbachu0604 Sep 15, 2016

@yaphatak : I am still getting the same error

pavanbachu0604 commented Sep 15, 2016

@yaphatak : I am still getting the same error

@JamesRootNineAgile

This comment has been minimized.

Show comment
Hide comment
@JamesRootNineAgile

JamesRootNineAgile Sep 15, 2016

The key thing that fixes the problem is
sudo chmod 777 /var/db/lockdown
This won't survive a reboot and the problem returns, related to libimobiledevice/libimobiledevice#356

JamesRootNineAgile commented Sep 15, 2016

The key thing that fixes the problem is
sudo chmod 777 /var/db/lockdown
This won't survive a reboot and the problem returns, related to libimobiledevice/libimobiledevice#356

@briananderson1222

This comment has been minimized.

Show comment
Hide comment
@briananderson1222

briananderson1222 Sep 15, 2016

@pavanbachu0604 the steps I provided are the steps I had to take to get to the current state mentioned in #6597 (comment) . Like I said these could be out of date but helped me get passed problems that arose while attempting to run our tests on a real device.

briananderson1222 commented Sep 15, 2016

@pavanbachu0604 the steps I provided are the steps I had to take to get to the current state mentioned in #6597 (comment) . Like I said these could be out of date but helped me get passed problems that arose while attempting to run our tests on a real device.

@skumar1122

This comment has been minimized.

Show comment
Hide comment
@skumar1122

skumar1122 Sep 15, 2016

@pavanbachu0604 @JamesRootNineAgile
Thank you guys for help,

I'm trying to do some real device Safari testing, it works on simulator but no on a real device with iOS 10.0 I get this error message:

WebDriverException: Message: An unknown server-side error occurred while processing the command. Original error: real device safari support not yet implemented. Contact an appium dev

So besides following all the steps from @briananderson1222, I cloned the WebDriverAgent source repo and replace the one provided in the npm appium dependency.

Anyone have tried something for real device Safari ?

skumar1122 commented Sep 15, 2016

@pavanbachu0604 @JamesRootNineAgile
Thank you guys for help,

I'm trying to do some real device Safari testing, it works on simulator but no on a real device with iOS 10.0 I get this error message:

WebDriverException: Message: An unknown server-side error occurred while processing the command. Original error: real device safari support not yet implemented. Contact an appium dev

So besides following all the steps from @briananderson1222, I cloned the WebDriverAgent source repo and replace the one provided in the npm appium dependency.

Anyone have tried something for real device Safari ?

@yaphatak

This comment has been minimized.

Show comment
Hide comment
@yaphatak

yaphatak Sep 15, 2016

Contributor

@skumar1122 It wont work now there is change that need to be done on appium side. And besides that you need to install ios-debug-proxy from head brew install --HEAD

Contributor

yaphatak commented Sep 15, 2016

@skumar1122 It wont work now there is change that need to be done on appium side. And besides that you need to install ios-debug-proxy from head brew install --HEAD

@qakapil

This comment has been minimized.

Show comment
Hide comment
@qakapil

qakapil Sep 15, 2016

Hi,
I followed the steps mentioned by @skumar1122 above and had some sort of success in setting up appium-xcuitest-driver. Here is my environment info -
appium-xcuitest-driver@2.0.12.
Xcode 7.3.2
iPhone iOS 9.1 (Will try on iOS10 in a few days.
In WebDriverAgent.xcodeproj/project.pbxproj I had to change values of IPHONEOS_DEPLOYMENT_TARGET from 9.3 to 9.1

I also set following two values in desiredCapablities -
'automationName': "xcuitest",
'realDeviceLogger':'/usr/local/bin/idevicesyslog'

After this I tried running my old python appium script. It did install the App on the device, launched the app,
self.driver.find_element(_self.username_locator).clear() - worked fine
self.driver.find_element(_self.sign_in_locator).click() - worked fine
However,
self.driver.find_element(*self.username_locator).send_keys('blablabla) is failing.

Is it because send_keys() method is using uiautomation ?
Or because I am using iOS9.1 ?
Or maybe because I am on Xcode 7.3.1 ?

Regards,
Kapil.

qakapil commented Sep 15, 2016

Hi,
I followed the steps mentioned by @skumar1122 above and had some sort of success in setting up appium-xcuitest-driver. Here is my environment info -
appium-xcuitest-driver@2.0.12.
Xcode 7.3.2
iPhone iOS 9.1 (Will try on iOS10 in a few days.
In WebDriverAgent.xcodeproj/project.pbxproj I had to change values of IPHONEOS_DEPLOYMENT_TARGET from 9.3 to 9.1

I also set following two values in desiredCapablities -
'automationName': "xcuitest",
'realDeviceLogger':'/usr/local/bin/idevicesyslog'

After this I tried running my old python appium script. It did install the App on the device, launched the app,
self.driver.find_element(_self.username_locator).clear() - worked fine
self.driver.find_element(_self.sign_in_locator).click() - worked fine
However,
self.driver.find_element(*self.username_locator).send_keys('blablabla) is failing.

Is it because send_keys() method is using uiautomation ?
Or because I am using iOS9.1 ?
Or maybe because I am on Xcode 7.3.1 ?

Regards,
Kapil.

@acdurai

This comment has been minimized.

Show comment
Hide comment
@acdurai

acdurai Sep 16, 2016

@imurchie

am getting the below mentioned error while running the test in ios 10

xcode 8
appium 1.6.0 beta
ios 10

at GeneratorFunctionPrototype.invoke (/usr/local/lib/node_modules/appium/node_modules/babel-runtime/regenerator/runtime.js:136:37)
[XCUITest] Shutting down WebDriverAgent
[debug] [XCUITest] Resetting simulator
[debug] [iOSLog] Stopping iOS log capture
[MJSONWP] Encountered internal error running command: Error: Unable to find real device logging program 'deviceconsole'
at WebDriverAgent.createRealDeviceLogsSubProcess$ (lib/webdriveragent.js:188:13)
at tryCatch (/usr/local/lib/node_modules/appium/node_modules/babel-runtime/regenerator/runtime.js:67:40)
at GeneratorFunctionPrototype.invoke as _invoke
at GeneratorFunctionPrototype.prototype.(anonymous function) as next
at GeneratorFunctionPrototype.invoke (/usr/local/lib/node_modules/appium/node_modules/babel-runtime/regenerator/runtime.js:136:37)
[HTTP] <-- POST /wd/hub/session 500 5043 ms - 195

acdurai commented Sep 16, 2016

@imurchie

am getting the below mentioned error while running the test in ios 10

xcode 8
appium 1.6.0 beta
ios 10

at GeneratorFunctionPrototype.invoke (/usr/local/lib/node_modules/appium/node_modules/babel-runtime/regenerator/runtime.js:136:37)
[XCUITest] Shutting down WebDriverAgent
[debug] [XCUITest] Resetting simulator
[debug] [iOSLog] Stopping iOS log capture
[MJSONWP] Encountered internal error running command: Error: Unable to find real device logging program 'deviceconsole'
at WebDriverAgent.createRealDeviceLogsSubProcess$ (lib/webdriveragent.js:188:13)
at tryCatch (/usr/local/lib/node_modules/appium/node_modules/babel-runtime/regenerator/runtime.js:67:40)
at GeneratorFunctionPrototype.invoke as _invoke
at GeneratorFunctionPrototype.prototype.(anonymous function) as next
at GeneratorFunctionPrototype.invoke (/usr/local/lib/node_modules/appium/node_modules/babel-runtime/regenerator/runtime.js:136:37)
[HTTP] <-- POST /wd/hub/session 500 5043 ms - 195

@imurchie

This comment has been minimized.

Show comment
Hide comment
@babusurendra

This comment has been minimized.

Show comment
Hide comment
@babusurendra

babusurendra Sep 16, 2016

Hi @imurchie , what is the expected date to release appium 1.6 goldmaster?

babusurendra commented Sep 16, 2016

Hi @imurchie , what is the expected date to release appium 1.6 goldmaster?

@acdurai

This comment has been minimized.

Show comment
Hide comment
@acdurai

acdurai Sep 16, 2016

@imurchie

Thanks for sharing the link, that issue fixed am getting below issue

Signing for "WebDriverAgentRunner" requires a development team. Select a development team in the project editor.
Code signing is required for product type 'UI Testing Bundle' in SDK 'iOS 10.0'

** TEST FAILED **

The following build commands failed:
Check dependencies
(1 failure)

[XCUITest] xcodebuild exited with code '65' and signal 'null'
[XCUITest] Error: xcodebuild failed with code 65
at SubProcess. (lib/webdriveragent.js:236:25)
at emitTwo (events.js:106:13)
at SubProcess.emit (events.js:191:7)
at ChildProcess. (lib/teen_process.js:191:14)
at emitTwo (events.js:106:13)
at ChildProcess.emit (events.js:191:7)
at Process.ChildProcess._handle.onexit (internal/child_process.js:215:12)
Error: xcodebuild failed with code 65
at SubProcess. (lib/webdriveragent.js:236:25)
at emitTwo (events.js:106:13)
at SubProcess.emit (events.js:191:7)
at ChildProcess. (lib/teen_process.js:191:14)
at emitTwo (events.js:106:13)
at ChildProcess.emit (events.js:191:7)
at Process.ChildProcess._handle.onexit (internal/child_process.js:215:12)
[XCUITest] Shutting down WebDriverAgent
[XCUITest] System log exited with code '0'
[debug] [XCUITest] Resetting simulator
[debug] [iOSLog] Stopping iOS log capture
[MJSONWP] Encountered internal error running command: Error: xcodebuild failed with code 65
at SubProcess. (lib/webdriveragent.js:236:25)
at emitTwo (events.js:106:13)
at SubProcess.emit (events.js:191:7)
at ChildProcess. (lib/teen_process.js:191:14)
at emitTwo (events.js:106:13)
at ChildProcess.emit (events.js:191:7)
at Process.ChildProcess._handle.onexit (internal/child_process.js:215:12)
[HTTP] <-- POST /wd/hub/session 500 59341 ms - 167

acdurai commented Sep 16, 2016

@imurchie

Thanks for sharing the link, that issue fixed am getting below issue

Signing for "WebDriverAgentRunner" requires a development team. Select a development team in the project editor.
Code signing is required for product type 'UI Testing Bundle' in SDK 'iOS 10.0'

** TEST FAILED **

The following build commands failed:
Check dependencies
(1 failure)

[XCUITest] xcodebuild exited with code '65' and signal 'null'
[XCUITest] Error: xcodebuild failed with code 65
at SubProcess. (lib/webdriveragent.js:236:25)
at emitTwo (events.js:106:13)
at SubProcess.emit (events.js:191:7)
at ChildProcess. (lib/teen_process.js:191:14)
at emitTwo (events.js:106:13)
at ChildProcess.emit (events.js:191:7)
at Process.ChildProcess._handle.onexit (internal/child_process.js:215:12)
Error: xcodebuild failed with code 65
at SubProcess. (lib/webdriveragent.js:236:25)
at emitTwo (events.js:106:13)
at SubProcess.emit (events.js:191:7)
at ChildProcess. (lib/teen_process.js:191:14)
at emitTwo (events.js:106:13)
at ChildProcess.emit (events.js:191:7)
at Process.ChildProcess._handle.onexit (internal/child_process.js:215:12)
[XCUITest] Shutting down WebDriverAgent
[XCUITest] System log exited with code '0'
[debug] [XCUITest] Resetting simulator
[debug] [iOSLog] Stopping iOS log capture
[MJSONWP] Encountered internal error running command: Error: xcodebuild failed with code 65
at SubProcess. (lib/webdriveragent.js:236:25)
at emitTwo (events.js:106:13)
at SubProcess.emit (events.js:191:7)
at ChildProcess. (lib/teen_process.js:191:14)
at emitTwo (events.js:106:13)
at ChildProcess.emit (events.js:191:7)
at Process.ChildProcess._handle.onexit (internal/child_process.js:215:12)
[HTTP] <-- POST /wd/hub/session 500 59341 ms - 167

@imurchie

This comment has been minimized.

Show comment
Hide comment
@imurchie

imurchie Sep 16, 2016

Member

Yes. Things need to be signed correctly.

appium/appium-xcuitest-driver#106

Member

imurchie commented Sep 16, 2016

Yes. Things need to be signed correctly.

appium/appium-xcuitest-driver#106

@iamola

This comment has been minimized.

Show comment
Hide comment
@iamola

iamola Sep 16, 2016

@imurchie Any update or workaround on this issue? My team and I saw this way too late.

iamola commented Sep 16, 2016

@imurchie Any update or workaround on this issue? My team and I saw this way too late.

@imurchie

This comment has been minimized.

Show comment
Hide comment
@imurchie

imurchie Sep 16, 2016

Member

I'm sorry. This is a 80+ comment thread with no cohesion. I have no idea
what "this issue" is anymore.

On Friday, September 16, 2016, iamola notifications@github.com wrote:

@imurchie https://github.com/imurchie Any update or workaround on this
issue? My team and I saw this way too late.


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#6597 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/ACfkUrMiN0P_1i3JyTDcS69DEoeV1QsZks5qqvvGgaJpZM4I4Kkc
.

Member

imurchie commented Sep 16, 2016

I'm sorry. This is a 80+ comment thread with no cohesion. I have no idea
what "this issue" is anymore.

On Friday, September 16, 2016, iamola notifications@github.com wrote:

@imurchie https://github.com/imurchie Any update or workaround on this
issue? My team and I saw this way too late.


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#6597 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/ACfkUrMiN0P_1i3JyTDcS69DEoeV1QsZks5qqvvGgaJpZM4I4Kkc
.

@imurchie

This comment has been minimized.

Show comment
Hide comment
@imurchie

imurchie Sep 16, 2016

Member

I'm sorry. This is a 80+ comment thread with no cohesion. I have no idea
what "this issue" is anymore.

On Friday, September 16, 2016, iamola <notifications@github.com
javascript:_e(%7B%7D,'cvml','notifications@github.com');> wrote:

@imurchie https://github.com/imurchie Any update or workaround on this
issue? My team and I saw this way too late.


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#6597 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/ACfkUrMiN0P_1i3JyTDcS69DEoeV1QsZks5qqvvGgaJpZM4I4Kkc
.

Member

imurchie commented Sep 16, 2016

I'm sorry. This is a 80+ comment thread with no cohesion. I have no idea
what "this issue" is anymore.

On Friday, September 16, 2016, iamola <notifications@github.com
javascript:_e(%7B%7D,'cvml','notifications@github.com');> wrote:

@imurchie https://github.com/imurchie Any update or workaround on this
issue? My team and I saw this way too late.


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#6597 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/ACfkUrMiN0P_1i3JyTDcS69DEoeV1QsZks5qqvvGgaJpZM4I4Kkc
.

@iamola

This comment has been minimized.

Show comment
Hide comment
@iamola

iamola Sep 16, 2016

@imurchie "The fact remains that Apple dropped Instruments support in Xcode 8, and Appium uses Instruments to automate the device."

iamola commented Sep 16, 2016

@imurchie "The fact remains that Apple dropped Instruments support in Xcode 8, and Appium uses Instruments to automate the device."

@imurchie

This comment has been minimized.

Show comment
Hide comment
@imurchie

imurchie Sep 16, 2016

Member

Yes. We are hard at work to provide the same level of support with the new
tools.

On Friday, September 16, 2016, Olajide Olaolorun notifications@github.com
wrote:

@imurchie https://github.com/imurchie "The fact remains that Apple
dropped Instruments support in Xcode 8, and Appium uses Instruments to
automate the device."


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#6597 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/ACfkUsZDPBDvV_iuBSxMsHRoRpxz7cq-ks5qqv8NgaJpZM4I4Kkc
.

Member

imurchie commented Sep 16, 2016

Yes. We are hard at work to provide the same level of support with the new
tools.

On Friday, September 16, 2016, Olajide Olaolorun notifications@github.com
wrote:

@imurchie https://github.com/imurchie "The fact remains that Apple
dropped Instruments support in Xcode 8, and Appium uses Instruments to
automate the device."


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#6597 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/ACfkUsZDPBDvV_iuBSxMsHRoRpxz7cq-ks5qqv8NgaJpZM4I4Kkc
.

@JaniJegoroff

This comment has been minimized.

Show comment
Hide comment
@JaniJegoroff

JaniJegoroff Sep 16, 2016

Member

@imurchie I'm trying out the latest beta build with Ruby bindings. So far I have come across with one major issue:

timed out after 30 seconds (underlying webdriver instance does not support javascript) (Selenium::WebDriver::Error::TimeOutError)

There are couple of Ruby binding methods that ends up calling execute_script method:
https://github.com/appium/ruby_lib/blob/master/lib/appium_lib/ios/helper.rb#L554

I guess this is same issue as #5623
I would like to tackle this issue since it fails so many tests.

Member

JaniJegoroff commented Sep 16, 2016

@imurchie I'm trying out the latest beta build with Ruby bindings. So far I have come across with one major issue:

timed out after 30 seconds (underlying webdriver instance does not support javascript) (Selenium::WebDriver::Error::TimeOutError)

There are couple of Ruby binding methods that ends up calling execute_script method:
https://github.com/appium/ruby_lib/blob/master/lib/appium_lib/ios/helper.rb#L554

I guess this is same issue as #5623
I would like to tackle this issue since it fails so many tests.

@shay777

This comment has been minimized.

Show comment
Hide comment
@shay777

shay777 Sep 18, 2016

I find this thread very useful but I still have one issue that was not resolved.
I use the beta version of appium 6, xcode 8 and ios 10. I cannot install my app on the device.
I had some of the errors that were mention here and I followed the solutions so there is a progress but now I have the error of:
Encountered internal error running command: Error: xcodebuild failed with code 65
Any idea how to solve this error?

shay777 commented Sep 18, 2016

I find this thread very useful but I still have one issue that was not resolved.
I use the beta version of appium 6, xcode 8 and ios 10. I cannot install my app on the device.
I had some of the errors that were mention here and I followed the solutions so there is a progress but now I have the error of:
Encountered internal error running command: Error: xcodebuild failed with code 65
Any idea how to solve this error?

@qakapil

This comment has been minimized.

Show comment
Hide comment
@qakapil

qakapil Sep 18, 2016

Hi @imurchie,
I build appium from source (master branch) and now I am able to launch WebdriverAgent and run my tests on iOS10 device. I am running this with Xcode 8. There is one minor issue which I am facing though. Even though WebdriverAgent gets installed on the device and my tests starts executing, on the console of appium logs, I continuously see this log message
[debug] [XCUITest] Waiting for WebDriverAgent server to finish loading...

I only see this log message with iOS10 device and not with iOS9.
I guess some logic needs to be changed in lib/webdriveragent.js

qakapil commented Sep 18, 2016

Hi @imurchie,
I build appium from source (master branch) and now I am able to launch WebdriverAgent and run my tests on iOS10 device. I am running this with Xcode 8. There is one minor issue which I am facing though. Even though WebdriverAgent gets installed on the device and my tests starts executing, on the console of appium logs, I continuously see this log message
[debug] [XCUITest] Waiting for WebDriverAgent server to finish loading...

I only see this log message with iOS10 device and not with iOS9.
I guess some logic needs to be changed in lib/webdriveragent.js

@shay777

This comment has been minimized.

Show comment
Hide comment
@shay777

shay777 Sep 18, 2016

is there any solution for this error:
Signing for "WebDriverAgentRunner" requires a development team. Select a development team in the project editor.
Code signing is required for product type 'UI Testing Bundle' in SDK 'iOS 10.0'

shay777 commented Sep 18, 2016

is there any solution for this error:
Signing for "WebDriverAgentRunner" requires a development team. Select a development team in the project editor.
Code signing is required for product type 'UI Testing Bundle' in SDK 'iOS 10.0'

@yaphatak

This comment has been minimized.

Show comment
Hide comment
@yaphatak

yaphatak Sep 18, 2016

Contributor

Can you make sure your xcode project editor for WDA looks like this
appium/appium-xcuitest-driver#106 (comment)

Contributor

yaphatak commented Sep 18, 2016

Can you make sure your xcode project editor for WDA looks like this
appium/appium-xcuitest-driver#106 (comment)

@shay777

This comment has been minimized.

Show comment
Hide comment
@shay777

shay777 Sep 19, 2016

thanks for your reply.
it's still not working.
I have the same error message

shay777 commented Sep 19, 2016

thanks for your reply.
it's still not working.
I have the same error message

@chaoleona

This comment has been minimized.

Show comment
Hide comment
@chaoleona

chaoleona Sep 19, 2016

I has updated appium to 1.6.0 beta1, xcode to 10, and run my test app in my iPhone SE, but the tap or click take much more time than before. A click may take 40s, and the console print many logs like "[debug] [XCUITest] Waiting for WebDriverAgent server to finish loading...". In simulator, it is much faster. How to improve this problem?

chaoleona commented Sep 19, 2016

I has updated appium to 1.6.0 beta1, xcode to 10, and run my test app in my iPhone SE, but the tap or click take much more time than before. A click may take 40s, and the console print many logs like "[debug] [XCUITest] Waiting for WebDriverAgent server to finish loading...". In simulator, it is much faster. How to improve this problem?

@jlipps

This comment has been minimized.

Show comment
Hide comment
@jlipps

jlipps Sep 19, 2016

Member

Since this thread has devolved into reporting of many different issues, I am closing it. If your particular issue is not yet resolved, please open a new issue and ensure to use the template to give us all the information which is specific to your issue. That will help us triage and fix as many things as we can with the new XCUITest support.

Member

jlipps commented Sep 19, 2016

Since this thread has devolved into reporting of many different issues, I am closing it. If your particular issue is not yet resolved, please open a new issue and ensure to use the template to give us all the information which is specific to your issue. That will help us triage and fix as many things as we can with the new XCUITest support.

@jlipps jlipps closed this Sep 19, 2016

@appium appium locked and limited conversation to collaborators Sep 22, 2016

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.