-
-
Notifications
You must be signed in to change notification settings - Fork 760
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
Appium 1.7.0 crashes Java client 5.0.3 when testing iOS #732
Comments
@welnanick I think that something is wrong on the server side. |
@welnanick Can you please attach full server log? It seems like you don't provide all the required capabilities. |
@TikhomirovSergey iOS works fine with 1.7.0 and latest java client. @welnanick can you share your sample driver creation code as @mykola-mokhnach suggested along with the pom or gradle file. |
Here is the code I am using to create the driver:
With all the system properties defined the above code should result in the following capabilities:
Again this works for Android, and not iOS, and it worked fine with 1.7.0 Beta. It wasn't until I updated appium yesterday morning that I started having issues. Here is a gist of the full appium logs up to the crash using the java-client: gist Also, just discovered appium-desktop is not working as I thought it was, as it can't interact with the 1.7.0 server, so I can't send commands. |
Oh, here are my dependencies in gradle:
|
@welnanick i will check in sometime and update you. |
@TikhomirovSergey the exception is thrown inside: default Map<String, Object> getSessionDetails() {
Response response = execute(GET_SESSION);
return ImmutableMap.<String, Object>builder()
.putAll(Map.class.cast(response.getValue())).build();
} We try to create immutable map on response values, but there is a key with null value there and this causes failure. Probably, it is necessary to perform some preliminary filtering before calling putAll |
@mykola-mokhnach Maybe. I will try to improve it soon. @welnanick said
So this is really intresting deatail |
...maybe some empty string was there |
Fix is going to be published.. |
@TikhomirovSergey is there an ETA for when the fix will be published? My iOS testing is currently completely halted due to this bug. |
@welnanick We are planning to release 5.1.0 or 5.0.4 soon though there is no exact ETA. I wanted test everything on Selenium 3.6.0 released yesterday before we make a java-client 5.1.0 or 5.0.4. Will keep you posted. |
@SrinivasanTarget I've encountered same problem with Versions: |
I don't expect any issues as there is not much changes in Selenium 3.6.0. Will check it though. I think you should give a try in latest java client without excluding selenium and adding it again.It should working without any efforts. |
…-client into readperformancedata * 'readperformancedata' of https://github.com/heeseon/java-client: (156 commits) build error Do not hardcode Do not hardcode Update README.md Update README.md Code style issues which were found by reviewer were fixed Code style issues which were found by reviewer were fixed The addition to appium#738 - following dependencies were updated: `org.seleniumhq.selenium:selenium-java` to 3.6.0 `com.google.code.gson:gson` to 2.8.2 `org.springframework:spring-context` to 5.0.0.RELEASE `org.aspectj:aspectjweaver` to 1.8.11 do not zero out implicit wait during location call rename DEFAULT_IMPLICITLY_WAIT_TIMEOUT to DEFAULT_TIMEOUT Update README.md some minor things that were found by reviewers were improved code style issues were got fixed appium#732 FIX ServerBuilderTest: ip calculation was improved ServerBuilderTest: the path resolving ServerBuilderTest: magic strings were turned into final values ServerBuilderTest: magic strings were turned into final values ServerBuilderTest: code improvement. Tests of local appium DriverService were re-designed. ...
I had recently updated to Xcode 9.2. Appium 1.6.3 was not compatible with this Xcode version. Here are the versions which are working with Xcode 9.2 |
Hi, Error: I am using |
@kumarRaghavendra Unfortunately cant help anything here. Give a try in latest java client and raise us issues if you hit any with detailed server logs. |
Hi, Is there any common method or any code snippet, which i can use to scroll and swipe in both android and iOS |
i am using below appium and selenium versions Selenium Version : 3.6.0 I am trying to do scroll and swipe, but i am getting the following error, please help me: [RemoteTestNG] detected TestNG version 6.13.1 SKIPPED CONFIGURATION: @AfterTest tearDown |
Hello I also had some issues, the only way that I make the test cases work is using the following configuration:
I tried a lots of combinations and this one is more or less working. The test cases fails, seems like some elements are not recognized. I am investigating why. For example, If I change the appium version to 5.0.4 the elements are not recognized: On the other hand, I couldn't start the selenium-java to an upper version I have this issue: |
Hello, Versions: Capabilities: Log: Appium log:
|
@victor-kalmus-techery Try to upgrade your client to the recent beta version |
Hi,
Appium log snippet: gist |
@mykola-mokhnach Please do the needful. |
@mykola-mokhnach Thanks a lot.. It worked... |
Description
When attempting to use java-client 5.0.3 to test an iOS device with Appium 1.7.0, the java-client crashes with java.lang.NullPointerException: null value in entry: browserName=null
Environment
Details
Using the same Appium Server, I can use appium-desktop using the custom server option to connect to the iOS device just fine. Android is unaffected. I believe this chunk of the logs are could relevant:
Code To Reproduce Issue [ Good To Have ]
Just attempt to connect to a real iOS device
Ecxeption stacktraces
gist
The text was updated successfully, but these errors were encountered: