Appium 1.5.1 Released!

NOTE: Appium 1.5.1 is a bug-fix release.


  • allow platformName to be any case
  • Windows process handling is cleaned up
  • Desired capabilities language and locale added


  • iOS 9.3 (Xcode 7.3) support
  • Fix handling of return values from executeScript in Safari
  • Don’t stop if Instruments doesn’t shut down in a timely manner
  • Escape single quotes in all methods that set the value on an element
  • Allow custom device names
  • Make full use of process arguments to Instruments
  • Pass launchTimeout to Instruments when checking devices


  • Make use of --bootstrap-port server argument
  • Fix keystorePassword capability to allow a string
  • Fix handling of localization in Android 6
  • Use Appium’s unlock logic for Chrome sessions
  • Make sure reset works
  • Make unlock more reliable for later versions of Android
  • Allow Xpath searching from the context of another element
  • Make full use of process arguments to adb
  • Better error messages when ChromeDriver fails to start

Release notes:


failed to install with:

npm ERR! Darwin 15.3.0
npm ERR! argv "/usr/local/Cellar/node/5.6.0/bin/node" "/usr/local/bin/npm" "install" "-g" "[email protected]"
npm ERR! node v5.6.0
npm ERR! npm  v3.6.0
npm ERR! path /usr/local/bin/appium
npm ERR! code EEXIST

npm ERR! Refusing to delete /usr/local/bin/appium: ../lib/node_modules/appium/bin/appium.js symlink target is not controlled by npm /usr/local
npm ERR! File exists: /usr/local/bin/appium
npm ERR! Move it away, and try again.

npm ERR! Please include the following file with any support request:
npm ERR!     /Users/Aleksei/npm-debug.log
npm ERR! code 1

subsequent “npm install -g [email protected]” completing successfully

@Aleksei, can you please remove /usr/local/bin/appium file using ‘sudo’ and try again to install latest one. because i was able to upgrade appium 1.5 to 1.5.1 without any issue.

@Priyank_Shah are you getting
Welcome to Appium v1.5.0 (REV dc865428e6a78ed6b8153132d6e50b9afc8c4570)
or it just me.


Seem like @isaac missed to update this as revision number is correct dc86542.

@pr4bh4sh, no i was able to launch 1.5.1 successfully.

[Appium] Welcome to Appium v1.5.1 (REV 7abc8c03f8a74a0fed4f409326c58796855c7ff7)
[Appium] Appium REST http interface listener started on

i think you did not upgrade your appium.

Priyank Shah

@Priyank_Shah Thanks for confirmation, I’m running from source so I’ll get a fresh clone and try.

thanks. helped.
(remove logs - either will read the thread :slight_smile: )

Does it also work with 10.11mac iOS version?

Yes it works with 10.11.4 I am currently using Appium 1.5.1 with 10.11.4 mac OS

How to install it? And where to install it from on appium site it is still showing 1.4 versions
When I downloaded 1.5.1 as a zip which file do i have to run?to install apium?

Appium 1.5.1 cannot be installed by avm.
Look at the issue here,

I just fixed the issue for avm install Appium 1.5.1.

Because some file path is changed in Appium 1.5, so avm cannot install it.
I make the change for avm file, then it can install all Appium versions.

  1. in ‘activate’ function, link “node_modules/appium/build/lib/main.js” to “bin/appium”.
  2. in ‘execute_with_version’ function, use “node_modules/appium/build/lib/main.js” to start Appium.

Install nodejs from here and then install Appium 1.5.1 through npm.

npm install -g appium

what are the steps to upgrade appium?

npm install -g appium will automatically pull latest stable version of Appium.

Hi, pr4bh4sh, I was wondering if there’s a GUI version for 1.5.1 just like 1.4.13 which has Inspector to use? That would be great! If not so, what can we use to inspect element? Thanks for your effort for all of the appium users and Looking forward to your suggestion :slight_smile:

There isn’t any GUI version after 1.4.13.
Using inspector

  1. Android - use uiautomatorviewer, it does not provide XPath though. If you need XPath you need to create it yourself.

  2. iOS - Not working on any iOS application automation project for a long time, however, @wreed or @Priyank_Shah (not sure who) has commented on some thread, Here’re the steps

  3. On your test script set a breakpoint just after the driver creation.

  4. Open the GUI version of Appium you have and click on the Inspector button. It should work as if you have started the appium from GUI mode.

Additional tip:

  1. If you are starting Appium on custom port make sure you change the port on GUI versions setting section.
  2. Make sure you have set commandTimeout when starting the server or in caps. So Appium server does not kill the session due to inactivity. I generally user 72000 seconds.

And thanks for the appreciation.


As other members suggested in this forum, you can keep 1.4.13 GUI app open and run the test in debug mode while Appium 1.5.1 server is running. Press the Inspector button on 1.4.13 GUI. you will be able to inspect the elements.
No need to press Launch button.

OK Got it. I just met a problem, which 1.4.13’s inspector shows the XPath is A, but when I use 1.5.1, it found another element, I have checked the code, so I doubt maybe there’s something difference in locating an element wtih XPath, that’s why I ask my question to you. And I’ll check more on my code and others.