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

imvenky · July 12, 2016, 7:40pm

Hi Jonahss,

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

Thanks in Advance,
Venkat

Russ · August 8, 2016, 5:22am

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

Russ · August 9, 2016, 12:42am

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

Yellowbeard · August 9, 2016, 1:23pm

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

Russ · August 10, 2016, 11:55pm

Pull Request #77 has been merged.

Tree · August 21, 2016, 10:45pm

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

cnotgo · August 24, 2016, 10:35pm

Does this work with all versions of iOS?

SergeVKom · August 25, 2016, 10:54am

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

pmck91 · September 21, 2016, 10:05am

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 · September 21, 2016, 1:36pm

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

Mayuresh_Shirodkar · September 25, 2016, 8:59pm

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 · September 25, 2016, 11:01pm

@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 · September 25, 2016, 11:06pm

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 · September 25, 2016, 11:07pm

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

Tree · September 25, 2016, 11:09pm

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

Mayuresh_Shirodkar · September 26, 2016, 2:40pm

Thanks @Tree for this.

Mayuresh_Shirodkar · September 26, 2016, 3:08pm

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 · September 26, 2016, 9:50pm

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 ideviceinstaller fails with "Could not connect to lockdownd. Exiting." · Issue #48 · libimobiledevice/ideviceinstaller · GitHub 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

github.com/libimobiledevice/libimobiledevice

ERROR: Could not connect to lockdownd, error code -2

opened 09:51PM - 12 Oct 15 UTC

Redskies

Spend several hours trying to figure this out but with no luck. I reinstalled (l…ibimobiledevice - 1.2.0) from the source (including libplist-1.12, ifuse-1.1.3 and libusbmuxd-1.1.0). I have no parental restrictions on the device and no screen lock. The device will not mount through linux and ifuse returns the same errors. I am using CAINE linux (ubuntu 14.04) which might be the problem, i don't know. I double checked the lockdown file to ensure the permissions are correct (as you can see below.) I'm pretty much at a dead end. Redskies:~$ idevice_id -l da27a7e9b8150f5822c8d2cbeeb58f73baab1268 Redskies:~$ ideviceinfo -s BasebandCertId: 3554301762 BasebandKeyHashInformation: AKeyStatus: 2 SKeyHash: 7MQEUyvzG4gjjZc7KsNNAVTS8g4= SKeyStatus: 0 BasebandSerialNumber: M4KIHQ== BasebandVersion: 6.00.00 BoardId: 10 BuildVersion: 13A344 ChipID: 35152 DeviceClass: iPhone DeviceColor: #3b3b3c DeviceName: iPhone DieID: 1522290294251032272 HardwareModel: N48AP PartitionType: ProductName: iPhone OS ProductType: iPhone5,3 ProductVersion: 9.0 ProductionSOC: true ProtocolVersion: 2 TelephonyCapability: true UniqueChipID: 3787524586761 UniqueDeviceID: da27a7e9b8150f5822c8d2cbeeb58f73baab1268 WiFiAddress: 6c:94:f8:2a:80:81 Redskies:~$ ideviceinfo ERROR: Could not connect to lockdownd, error code -2 Redskies:~$ idevicepair pair ERROR: Please accept the trust dialog on the screen of device da27a7e9b8150f5822c8d2cbeeb58f73baab1268, then attempt to pair again. Redskies:~$ idevicepair pair SUCCESS: Paired with device da27a7e9b8150f5822c8d2cbeeb58f73baab1268 Redskies:~$ idevicepair validate ERROR: Device da27a7e9b8150f5822c8d2cbeeb58f73baab1268 returned unhandled error code -2 Redskies:~$ ls -l /lib/udev/rules.d/ total 604 -rwxrwxrwx 1 root Redskies 611 Oct 21 2013 85-usbmuxd.rules Redskies:~$ sudo chmod -R 0777 /var/lib/lockdown/ Redskies:~$ ls -l /var/lib/lockdown total 12 -rwxrwxrwx 1 root root 7821 Oct 12 10:27 da27a7e9b8150f5822c8d2cbeeb58f73baab1268.plist -rwxrwxrwx 1 root root 266 Oct 8 16:13 SystemConfiguration.plist Redskies:/var/lib$ ls -l total 316 drwxrwxrwx 2 root root 4096 Oct 12 10:27 lockdown Redskies:/media$ ifuse /media/iphone Failed to connect to lockdownd service on the device. Try again. If it still fails try rebooting your device. EDIT: when trying to run the system log Redskies:~$ sudo idevicesyslog ERROR: Could not start service com.apple.syslog_relay. Could not start logger for udid da27a7e9b8150f5822c8d2cbeeb58f73baab1268 ^C Exiting...

github.com/google/ios-webkit-debug-proxy

Could not connect to lockdownd. Exiting Permission denied

opened 08:54AM - 14 Sep 16 UTC

closed 12:18AM - 19 Sep 16 UTC

Can-too

I have installed the XCode upgrade to my iOS 7.3.1, to run my existing IPhone Ap…pium Tests using iOS 10. The some of my real mobile devices have also been upgraded but Since the upgrade to XCode my browser app tests all devices are failing. The ios-webkit-debug proxy has been having the same issue: Could not connect to lockdownd. Exiting Permission denied. Unable to attach <udid> inspector. I have continually booted/rebooted the mobile devices and the iMac Mini (El Captain). I have even tried uninstalling/reinstalling the ios_webkit_debug_proxy, but nothing has helped... It seems like the upgrade of the XCode 7.3.1 to include iOS 10 appears to be the issue because using the ios_webkit_debug_proxy with the iOS 9.3.5 devices, have also stopped working, failing with the same reason. I have since run SafariLauncher using XCode on both iOS 9.3.5 and 10.0.1. using idevice -l all my devices are listed, using idevicepair pair was a SUCCESS, BUT using idevicepair validate produces: ERROR: Device <udid> is not paired with this host Which seems to be a contradiction.... I have also tried using Instruments on the MAC but when I choose a device having 10.0.1 installed the recording button is not enabled and has the comment: "This instrument's supported recording mode are none". This may be of no interest - just something I noticed... Help....

github.com/libimobiledevice/ideviceinstaller

ideviceinstaller is not working with iOS 10.0 beta version(Could not connect to lockdownd. Exiting.)

opened 11:31AM - 20 Jul 16 UTC

closed 06:44PM - 27 Jul 16 UTC

AbMathur

I am using libimobiledevice in my iOS project. I upgrade my iphone 6sPlus to iOS… 10.0 beta version. i fired ideviceinfo command from my mac and get the response : Could not connect to lockdownd, error code -5 Any one know about this error?? when i am trying to install my ipa through ideviceinstaller, there I am having the following error: Could not connect to lockdownd. Exiting. please let me know if someone know's the solution!

Mayuresh_Shirodkar · September 27, 2016, 2:40am

@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 · September 27, 2016, 5:17pm

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.