Skip to content
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

When could we expect Appium server 1.6.0 version (.dmg file) to support IOS 10 automation #7011

Closed
pixyish opened this issue Oct 13, 2016 · 40 comments

Comments

@pixyish
Copy link

pixyish commented Oct 13, 2016

When could we expect Appium server 1.6.0 version (.dmg file) to support IOS 10 automation.

We are trying to automate IOS 10 using Appium. As I already know that Appium's 1.5.3 version don't support IOS 10. I tried to find out 1.6.0 version for Appium server (.dmg file) but I couldn't. Please share if you have any information regarding same.

And if there is any way to use appium's 1.6.0 beta version then please elaborate.

Any help would be appreciated!

@triager triager added the Needs Triage bugs which are not yet confirmed label Oct 13, 2016
@tanhaipeng
Copy link

the same question!

@babusurendra
Copy link

any updated on release date?

@imurchie
Copy link
Contributor

The person who works on it has said he will get on it early this week.

@babusurendra
Copy link

Thanks for the update @imurchie :)

I also have question here that how to launch simulator where appium installed through command "npm install appium -g "

@imurchie
Copy link
Contributor

When you start a session, if you don't specify a device it will launch a simulator.

@babusurendra
Copy link

@imurchie, I didnt specified any device i have used the command "appium" and it showing "Appium REST http interface listener started on 0.0.0.0:4723"

@imurchie
Copy link
Contributor

That is the server starting, not a session starting.

@kaftee
Copy link

kaftee commented Oct 19, 2016

@imurchie Until new .dmg will be deployed, is there any way to use inspector with Xcode8? I.e. build some artifacts from 1.6.0 and merge into 1.5.3?

@imurchie
Copy link
Contributor

Not without a lot of work.

You can, however, try https://github.com/mykola-mokhnach/Appium-iOS-Inspector

@kaftee
Copy link

kaftee commented Oct 19, 2016

@imurchie thanks. Using that tool is a bit annoying. Looking forward for Appium Inspector.

@Shanthadeepak
Copy link

How to install appium beta 1,6 version?

@pavanbachu0604
Copy link

npm install -g appium

@SimplyJaymin
Copy link

@imurchie Any updates on the 1.6.0 (.dmg file)?

@imurchie
Copy link
Contributor

I will post when there are any updates.

@Msbarari
Copy link

Any updates on the 1.6.0 (.dmg file)?

@mykola-mokhnach
Copy link
Collaborator

@triager please close

@triager triager closed this as completed Oct 27, 2016
@SimplyJaymin
Copy link

@triager The 1.6.0 dmg has not yet been released. Not sure why was this issue closed.

@mykola-mokhnach
Copy link
Collaborator

@JayminRaval why should we keep it opened instead? dmg release will be advertised separately in any case.

@SimplyJaymin
Copy link

@triager Fair point

@kaftee
Copy link

kaftee commented Oct 31, 2016

Has anyone figure out how to merge 1.6.x into 1.5.3?

@kommuswamy
Copy link

@imurchie ,any update om 1.6.0 .dmg file , when it will release?

@chenchaoyi
Copy link

If to use the Appium inspector is the reason you want to make Appium installer include 1.6.0, this might help you with different options.

@prahladsharma007
Copy link

any update for dmg of 1.6.0, can any one help to figure out how to get the xpath without Inspector

@mykola-mokhnach
Copy link
Collaborator

@prahladsharma007
Copy link

Thanks @mykola-mokhnach for your quick reply.

My application gets open but I am facing following error.

[HTTP] <-- GET /wd/hub/session/3469971c-1aaa-49ce-809f-21c758583bd9/contexts 500 187 ms - 219
[debug] [XCUITest] Waiting for WebDriverAgent server to finish loading...
[HTTP] --> GET /wd/hub/session/3469971c-1aaa-49ce-809f-21c758583bd9/source {}
[MJSONWP] Calling AppiumDriver.getPageSource() with args: ["3469971c-1aaa-49ce-809f-2...
[debug] [XCUITest] Executing command 'getPageSource'
[JSONWP Proxy] Proxying [POST /source] to [POST http://localhost:8100/session/6080DFA4-B734-4E7B-A433-13A892C468ED/source] with no body
[debug] [WebDriverAgent] Sim: Dec 1 16:30:49 l-44rq542 XCTRunner[95020]: Enqueue Failure: UI Testing Failure - Failure fetching attributes for element <XCAccessibilityElement: 0x600000243d20> Device element: Error Domain=XCTestManagerErrorDomain Code=13 "Error copying attributes -25202" UserInfo={NSLocalizedDescription=Error copying attributes -25202} 0 1
[debug] [WebDriverAgent] Sim: Dec 1 16:31:04 l-44rq542 XCTRunner[95020]: Enqueue Failure: UI Testing Failure - Failure fetching attributes for element <XCAccessibilityElement: 0x600000248d90> Device element: Error Domain=XCTestManagerErrorDomain Code=13 "Error copying attributes -25202" UserInfo={NSLocalizedDescription=Error copying attributes -25202} 0 1
[debug] [XCUITest] Waiting for WebDriverAgent server to finish loading...

Please help me out to solve this error.

@babusurendra
Copy link

babusurendra commented Dec 1, 2016

@imurchie , I am seeing that "killin all ios ios simulatros " error when launched the app through scripts .
it is launching and terminating the simulator two times .
i have appium 1.6.1 and iOS 10

also showing the bellow errors
[XCUITest] Simulator with udid '31F9EAAE-0174-4200-AECF-521F1491AB86' not booted. Booting up now
[debug] [iOSSim] Killing all iOS Simulators

can you help me on this?
@jlipps

@mykola-mokhnach
Copy link
Collaborator

@prahlad06 Known WDA issue: facebookarchive/WebDriverAgent#372

@babusurendra
Copy link

babusurendra commented Dec 1, 2016

@mykola-mokhnach i am able to access link :)

@prahladsharma007
Copy link

@mykola-mokhnach do you have any idea , when this WDA issue : facebookarchive/WebDriverAgent#372 will get fixed.
or if its already fixed then please let me know the Appium version.

@mykola-mokhnach
Copy link
Collaborator

@prahlad06 No idea. This issue is also pain in the $#$ for our automated tests and I'd like to have it fixed. You can add your comments to the master thread - maybe the project maintainer knows more.

@jeevan1524
Copy link

@babusurendra : I believe you have the appium 1.6.1 installed on your machine. If it is installed on a mac(.dmg file), can you please let me know where you found it?
I am badly waiting & searching for the appium 1.6.x dmg file all over the internet.

@babusurendra
Copy link

@jeevan1524 , I have installed appium 1.6.x with the command "npm install -g appium@1.6.3" . you can try that.

@jeevan1524
Copy link

jeevan1524 commented Dec 16, 2016

@babusurendra : I tried your method of installing appium 1.6.3 & was able to successfully install it on the Terminal. Thanks for that help.!!
My other question is - even after installing 1.6.3, when I open the "appium.app --> About appium" - I see the version to be "Version 1.5.3(Ara)". Shouldn't I be seeing 1.6.3 instead? Can you please help me on this?

@SimplyJaymin
Copy link

SimplyJaymin commented Dec 16, 2016 via email

@jeevan1524
Copy link

@JayminRaval : Thanks for your help. I tried to now start appium by typing "appium" in the Terminal - Looks like its working, got a message on the Terminal saying "Welcome to Appium 1.6.3 ...." So, this can be only started via Terminal and not through the app?

@SimplyJaymin
Copy link

SimplyJaymin commented Dec 16, 2016 via email

@jeevan1524
Copy link

@JayminRaval : Thank you for the info. But, I can still run my tests against appium 1.6.3 using the "start via Terminal" method right?

@SimplyJaymin
Copy link

SimplyJaymin commented Dec 16, 2016 via email

@praveen-cimplicity
Copy link

Appium 1.6.3 is not without problems as has been seen with Saucelabs. Opening it up to the industry can only help alleviate problems or work around the lack of instruments support in iOS 10 introduced by Apple.

@imurchie imurchie removed the Needs Triage bugs which are not yet confirmed label Apr 13, 2017
@lock
Copy link

lock bot commented Apr 28, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked and limited conversation to collaborators Apr 28, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests