6.0.0-BETA3 - PLATFORM_NAME cannot be resolved

[telangn]

Description

@SrinivasanTarget @mykola-mokhnach @TikhomirovSergey @jlipps
@saikrishna321

Going from BETA2 to BETA3, using the code below is giving me an issue, whereas in BETA2 it did not -

dc.setCapability(MobileCapabilityType.PLATFORM_NAME, Platform.ANDROID);

PLATFORM_NAME cannot be resolved is what my IDE is throwing now.

My only options are PLATFORM or PLATFORM_VERSION.
I have tried them and I get a console error that PLATFORM_NAME should be used and it couldn't start. But I cannot choose it when programming. Which one do I choose now?

org.openqa.selenium.WebDriverException: An unknown server-side error occurred while processing the command. Original error: You must include a platformName capability (WARNING: The server did not provide any stacktrace information)
Command duration or timeout: 63 milliseconds
Build info: version: '3.4.0', revision: 'unknown', time: 'unknown'
System info: host: 'ninad-Gazelle', ip: '127.0.1.1', os.name: 'Linux', os.arch: 'amd64', os.version: '4.13.0-36-generic', java.version: '1.8.0_151'
Driver info: driver.version: AppiumDriver

Also, What is the argument I pass as the Android OS? (instead of Platform.ANDROID)

Environment

io.appium - java-client - 6.0.0-BETA3
Ubuntu 16
Eclipse IDE

[saikrishna321]

Can you share your appium server logs

[TikhomirovSergey]

@telangn
Sorry for the late respnonse.

Build info: version: '3.4.0', revision: 'unknown', time: 'unknown'

I am seing this string and I suspect a dependency conflict there. Two last beta versions depend on Selenium 3.9.1. Could you update your project?

Also beta3 has some breaking changes which require server >= 1.8.0-beta3? Which server version do you use?

[telangn]

Hi @TikhomirovSergey @saikrishna321 ,
below are all the Selenium and Appium dependencies I have in my pom.xml currently.
What should I change?
Many thanks!

org.seleniumhq.selenium
selenium-java
3.4.0

io.appium
java-client
6.0.0-BETA3

If I run appium manually at the command line I get -
Welcome to Appium v1.7.1 (REV 02773af31860e14d247def718a25b16667e94012)

[SrinivasanTarget]

@telangn Remove Selenium dependency from your pom.xml and use the latest version of java client which is 6.0.0-BETA4 and do use the latest beta of appium server too. If you still face any issues, feel free to give us the server logs.

[telangn]

Can you give me the command line instruction to upgrade my appium server to the latest? @saikrishna321 @TikhomirovSergey

I have tried sudo npm install appium@1.8.0-beta3 and I get this -

ninad@ninad-Gazelle:~$ sudo npm install appium@1.8.0-beta3
npm WARN deprecated babel-core@5.8.24: Babel 5 is no longer being maintained. Upgrade to Babel 6.
npm WARN deprecated line-numbers@0.2.0: Copy its ~20 LOC directly into your code instead.
npm WARN deprecated minimatch@2.0.10: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue

> appium-chromedriver@3.4.0 install /home/ninad/node_modules/appium-chromedriver
> node install-npm.js

(node:7387) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): Error: EACCES: permission denied, mkdir '/home/ninad/node_modules/appium-chromedriver/201829-7387-15ky6cp.87b8h'
(node:7387) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
info Chromedriver Install Installing Chromedriver version '2.36' for platform 'linux' and architecture '64'
info Chromedriver Install Opening temp file to write chromedriver_linux64 to...
Error: EACCES: permission denied, mkdir '/home/ninad/node_modules/appium-chromedriver/201829-7387-rnogry.jeotb'
npm WARN enoent ENOENT: no such file or directory, open '/home/ninad/package.json'
npm WARN ninad No description
npm WARN ninad No repository field.
npm WARN ninad No README data
npm WARN ninad No license field.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.1.3 (node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.1.3: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! appium-chromedriver@3.4.0 install: `node install-npm.js`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the appium-chromedriver@3.4.0 install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/ninad/.npm/_logs/2018-03-09T17_32_54_853Z-debug.log
ninad@ninad-Gazelle:~$ 

[SrinivasanTarget]

@telangn

npm uninstall -g appium
npm install -g appium@beta

[telangn]

Thank you so much! Everything works now!
This issue can be closed. @TikhomirovSergey @saikrishna321