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

@Pranodayd Just try this Appium prallel device execution in multiple machines

Achieved it successfully.

Thanks

Any plan to support real device for xcuitest driver in future?

Hello,

Any update on the firm date? :slight_smile:

I am guessing it is soon, right? Because as far as I know iOS 10 is in public beta now, which probably means that the official release is getting real close.

Thanks in advance for replying.

Cheers,
Anna

P.S. Just a suggestion, but I think it would be a good idea to create a separate topic with a post informing the status of xcuitest-driver. I am betting that many ppl are asking the same questions in many different topics :slight_smile:

Hi Jonahss,

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

Thanks in Advance,
Venkat

1 Like

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}”

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

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

1 Like

Pull Request #77 has been merged.

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

Does this work with all versions of iOS?

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

1 Like

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.

1 Like

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

1 Like

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?

@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.

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?

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

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

1 Like

Thanks @Tree for this.