This site is in read only mode. Please continue to browse, but replying, likes, and other actions are disabled for now.
Are we have to waiting for new client (java client, python client, etc.) for full support of iOS 10 on real devices?
26 days later
@jonahss what is the expected date to release Appium 1.6 goldmaster?
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?
Thanks @Tree for this.
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
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/486 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
@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.
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.
Thanks for the info.
I already have a comprehensive documentation with me which I used to setup multiple Mac Minis for appium. All I'm looking now is support for iOS 10 devices while keeping support for iOS 8.x, 9.x.
Please advise.
Thanks.
@Mayuresh_Shirodkar: You can clone the code from GitHub and follow the below steps:
Clone the appium from the git : git clone https://github.com/appium/appium.git59
Point to the cloned folder
$ npm install
In case of the shrink-wrap error :
$ npm shrinkwrap
8 months later
Hi ,
I am referring @appum_gen questions , I need support. Need documentation to convert existing Appium 1.4.16 test suite conversion to Appium 1.6.5 to run test suites on IOS 10 physical devices. Same with Android 7.0 as well.
So far with Older versions Android and IOS successfully running using Findelementsby methods , but seeing changes in Appium 1.6.X (XCUITestFramework) , we bit confused and unable to find propert guidance for migration of existing test suite to newer appium version to support IOS 10 and Android 7 OS version.
Appreciate indeed help.
Regards,
Kiran