[iOS9 UIAutomation] What is Appium approach to UIAutomation deprecation by Apple

imvenky 2016-07-12 19:40:26 UTC #82

Hi Jonahss,

Can you please update on the Appium 1.6.0 release date with XCUITest support.

Thanks in Advance,
Venkat

Russ 2016-08-08 05:22:17 UTC #83

Hi,

I think there is a bug in appium-instruments for bin/xcode-iwd.sh.

It adds and sets environment variables including the word string for both DYLD_INSERT_LIBRARIES and LIB_PATH. If you edit the plist after running the shell script, the simulator will run without delay.

The resulting com.apple.instruments.deviceservice.plist includes:

<key>DYLD_INSERT_LIBRARIES</key>
<string>string ~/.nvm/versions/node/v6.3.1/lib/node_modules/appium-instruments/thirdparty/iwd7/DTMobileISShim.dylib</string>
<key>LIB_PATH</key>
<string>string ~/.nvm/versions/node/v6.3.1/lib/node_modules/appium-instruments/thirdparty/iwd7/</string>

when it should be:

<key>DYLD_INSERT_LIBRARIES</key>
<string>~/.nvm/versions/node/v6.3.1/lib/node_modules/appium-instruments/thirdparty/iwd7/DTMobileISShim.dylib</string>
<key>LIB_PATH</key>
<string>~/.nvm/versions/node/v6.3.1/lib/node_modules/appium-instruments/thirdparty/iwd7/</string>

Here is a script to test it:

#!/usr/bin/env bash

nvm install node
nvm alias default node
nvm use node

node_version=$(node --version)

npm install -g appium
npm install -g wd
npm install -g appium-instruments

xcode_path="/Applications/Xcode.app"
appium_instruments_path="$HOME/.nvm/versions/node/$node_version/lib/node_modules/appium-instruments"

sh "${appium_instruments_path}/bin/xcode-iwd.sh" "$xcode_path" "${appium_instruments_path}"

Does iwd work with xcode7.3.1 and appium 1.5.3

Russ 2016-08-09 00:42:35 UTC #84

I've submitted a Pull Request #77 to appium-instruments to fix this. https://github.com/appium/appium-instruments

Yellowbeard 2016-08-09 13:23:48 UTC #85

nice find @Russ - I applied your change locally and now testing on sim is really fast

Russ 2016-08-10 23:55:50 UTC #86

Pull Request #77 has been merged.

Tree 2016-08-21 22:45:13 UTC #87

@Venkat I can see in npm that there is now an appium 1.6.0-beta1 version available

cnotgo 2016-08-24 22:35:40 UTC #88

Does this work with all versions of iOS?

SergeVKom 2016-08-25 10:54:45 UTC #89

Are we have to waiting for new client (java client, python client, etc.) for full support of iOS 10 on real devices?

pmck91 2016-09-21 10:05:19 UTC #90

any update on this @jonahss? Id love to be able to move on to xcode 8 and ios 10 but no support of xcuitest is holding the team back. I can't let them release until test coverage is back up.

iharT 2016-09-21 13:36:43 UTC #91

@jonahss what is the expected date to release Appium 1.6 goldmaster?

Mayuresh_Shirodkar 2016-09-25 20:59:27 UTC #92

Hey @farnett did you get XCUItest working for your tests? Any work around for null sessionID issue?
Also did you run your tests on real devices?

Tree 2016-09-25 23:01:43 UTC #93

@farnett's issue was when using version 1.0.0 and 1.0.1. The current version is 2.0.16 and I do not believe the null sessionID has been a problem for any of the 2.x versions.

Mayuresh_Shirodkar 2016-09-25 23:06:07 UTC #94

Thanks for the reply @Tree . I was using Appium 1.6Beta1 where i got the error.
Switched to Appium 1.6beta2 ,looks good now. And able to run my tests on Real iOS device(9.x)

Is Appium 1.6beta2 the latest available on npm? Any idea if they have realsed newer Betas?

Tree 2016-09-25 23:07:44 UTC #95

Last I checked latest was 1.6.0 Beta 1 so beta 2 must have just been released in last few days

Tree 2016-09-25 23:09:28 UTC #96

also if you want to see all available versions you can try this
npm view appium versions -json

Mayuresh_Shirodkar 2016-09-26 14:40:05 UTC #97

Thanks @Tree for this.

Mayuresh_Shirodkar 2016-09-26 15:08:25 UTC #98

Does Appium 1.6.0Beta2 support Webview automation yet? Hybrid App Automation?
Any idea guys? Right now i am getting this error while conecting through ios-debug-proxy
Error:
Could not connect to lockdownd. Exiting.: Broken pipe
Unable to attach 7e4db10a24944189f626dc90cddf4fe3fa28099e inspector

For iOS10.0.1

Tree 2016-09-26 21:50:11 UTC #99

Could not connect to lockdownd
I have see an error like this with Appium 1.5.3 also. Seems like a file permission problem for ideviceinstaller.
Changing the file permission (sudo chmod -R 777 /var/db/lockdown/) as suggested in this thread https://github.com/libimobiledevice/ideviceinstaller/issues/48 worked for me but only as a tempaorary fix. As something changes it back and tests start failing again. I haven't found a permanent fix yet. This has only been a problem for us on one of our automation macs.

There seem to be a few different problems with lockdownd so maybe try installing you app manually using ideviceinstaller and inspect the message for the error code in case yours is a different problem

ideviceinstaller -u yourUDID -i path/to/your/app

Mayuresh_Shirodkar 2016-09-27 02:40:09 UTC #100

@Tree
Thanks for that.
Did some checks and thought of updating the dependencies.
This fixed it for me ultimately:
brew uninstall libimobiledevice && brew install --HEAD libimobiledevice
I needed to update my libmobiledevice to the latest available version as i was working on iOS 10.0.

appium_gen 2016-09-27 17:17:55 UTC #101

Looks awesome!

We're using Appium 1.4.16 with iOS 8.x/9.x versions and with Android 4.4/5.1/Marshmallow stuff. The apps we automate are moving to iOS 10.x and need to support them too.

Is there a step by step documentation for what needs to be done to upgrade from Appium 1.4.x to Appium 1.6 beta 2 (support for physical devices running on iOS 10.x) while also support the earlier versions of iOS. I also read that the desired capabilities has changed beginning with Appium 1.6.

Please advise.

Thanks.