This site is in read only mode. Please continue to browse, but replying, likes, and other actions are disabled for now.
Sep 2015
1 / 42
Sep 2015
Apr 2016
isaac
Sep '15

Hello Appium users!

As you may know, the core Appium team has been working tirelessly on rewriting Appium in the latest JavaScript, in order to make a more reliable system that is also more modular and more easily contributed-to. We are happy to announce the first public beta release from this process!

The new system requires at least Node.js 0.12 (the current is 0.12.7: https://nodejs.org/en/download/198).

To install, use npm install -g appium@beta, or, from source, checkout the 1.5 branch in the Appium repo (https://github.com/appium/appium/tree/1.5), remove all the old dependencies by running rm -rf node_modules and run npm install (there is a known issue in which this sometimes fails. If that happens, run npm install appium-chromedriver, and then re-run npm install). There is no longer any need to run a reset script.

Running appium ought to display that you are on Appium 1.5.0-beta4 (the 4 may be higher, as we fix things and release):

isaac@isaac: ~/code
👻 ➤ appium
info: [Appium] Welcome to Appium v1.5.0-beta4 (REV 0f1f3ed29c8c3c7b390b19070c8bbca5e3c8e6c0)
info: [Appium] Appium REST http interface listener started on 0.0.0.0:4723

This is a beta release. We have tested as much as we can, but need help finding as many issues as possible, before releasing fully. Toward that end, if you find anything, please file an issue in the Appium repo (https://github.com/appium/appium/issues) with the label 1.5-beta (https://github.com/appium/appium/labels/1.5-beta). As much information as you can provide would be helpful, but at a minimum we need the server output for the error, including any desired capabilities and configuration information.

There are, as of now, some known issues that are being worked on. To wit,

Android:

  • When installing from source, the npm dependencies often fail because of the Chromedriver package. To get around this, first run npm install appium-chromedriver and then npm install within the Appium repo.
  • Airplane mode - turning back on is flakey.

Thank you for helping out to make this the best, most stable version of Appium yet! We are really excited to get this out there into the world!

Best,

Isaac.

  • created

    Sep '15

  • last reply

    Apr '16
  • 41

    replies

  • 19.3k

    views

  • 21

    users

  • 5

    likes

  • 14

    links

Frequent Posters

Popular Links

402Appium 1.5 beta announcement · GitHub gist.github.com
220Download | Node.js nodejs.org
2061.4.14 fn must be a function · Issue #5814 · appium/appium · GitHub github.com
189Whats expected date for Appium 1.5 discuss.appium.io
84Extremely slow performance on Mac OSX 10.10.1 Yosemite · Issue #4397 · appium/appium... github.com

There are 41 replies with an estimated read time of 6 minutes.

pinned globally Sep 18, '15

hardik_d
Sep '15

i get following errors:

throw new Error("iOS Authorization has not been ported yet");

and

throw new Error("Appium doctor has not been ported yet");

don't we need these steps now?

hardik_d
Sep '15

following just 1.5 branch checkout and doing npm install i got following error:

Hardiks-MacBook-Pro:pnm_consumer hardik$ appium
module.js:338
throw err;
^
Error: Cannot find module '/Users/hardik/projects/mobile/mobile_consumer/src/pnm_consumer/appium/bin/appium.js'
at Function.Module._resolveFilename (module.js:336:15)
at Function.Module._load (module.js:278:25)
at Function.Module.runMain (module.js:501:10)
at startup (node.js:129:16)
at node.js:814:3

hardik_d
Sep '15

i just type in appium and it uses node to triggering appium.js

node $APPIUM_BIN/appium.js

isaac
Sep '15

from source you ought to be able to just run
node .

Alternatively,
node ./build/lib/main.js

hardik_d
Sep '15

so no need to run reset.sh, authorize-ios.js, appium-doctor.js ?

isaac
Sep '15

No more reset script. authorize-ios and appium-doctor are still around but are their own packages, and are under development.

npm install -g appium-doctor
appium-doctor

npm install -g authorize-ios
authorize-ios

The latter will be fixed and out forthwith. Sorry for the confusion.

bayandin
Sep '15

Hey guys, I was trying to play with 1.5.0-beta4 (from npm) for Mobile WebApp testing and I've found that driver can't even open URL:

...
info: [HTTP] --> POST /wd/hub/session/1a7c04e8-a982-44fa-b6a6-fd6ae56c4b7c/url {"url":"https://github.com/appium/appium"}
info: [MJSONWP] Calling AppiumDriver.setUrl() with args: ["https://github.com/appium/appium","1a7c04e8-a982-44fa-b6a6-fd6ae56c4b7c"]
info: [HTTP] <-- POST /wd/hub/session/1a7c04e8-a982-44fa-b6a6-fd6ae56c4b7c/url 500 2.469 ms - 122

All logs and code example are available here: https://gist.github.com/bayandin/d9542c5212db3046879615

9 days later
isaac
Sep '15
bayandin

Finally released beta 6, in which chrome/browser support in Android has been fixed. Sorry for the delay.

nv_sateesh
Oct '15

Hi Sruthi and Seleniumappiumnewbie,

----APP Getting crashed on simulators with iOS 9.0 version in Appium 1.4.13 and also ios 9.0 version is not displayed in Platform dropdown of APPIUM GUI. (I have Mac OS 10.11 and Xcode 7.0.1)

I have updated to Appium 1.4.13 successfully, also upgraded my mac
to the El Capitan new OS version 10.11 and Xcode to 7.0.1.....
1) After Xcode upgrade to 7.0.1 all the simulators iOS version is updated to 9.0..
2) But when i trying to update in APPIUM GUI the platform showing till
iOS version 8.4.... not showing the 9.0 Version......when start the appium server by
keeping 9.0 Version forcefully then app is getting crashed........

below is the error, which is displayed on appium logs.....

info: [debug] Attempting to run app on iPhone 6 (9.0) [

info: On xcode 7.0, instruments-without-delay does not work, skippinginstruments-without-delay
info:
[debug] Spawning instruments with command:
/Applications/Xcode.app/Contents/Developer/usr/bin/instruments -t
/Applications/Xcode.app/Contents/Applications/Instruments.app/Contents/PlugIns/AutomationInstrument.xrplugin/Contents/Resources/Automation.tracetemplate
-D /tmp/appium-instruments/instrumentscli0.trace -w "iPhone 6 (9.0) ["
/var/folders/6y/3w4t1jld3997y9q_6cvwswqr0000gn/T/11598-5518-63ryqs/Payload/TheWeather.app
-e UIASCRIPT "/Users/monocept/Library/Application
Support/appium/bootstrap/bootstrap-e16e825cd345231b.js" -e
UIARESULTSPATH /tmp/appium-instruments
info: [debug] And launch timeouts (in ms): {"global":90000}

info: [debug] [INST STDERR] 2015-10-08 11:00:21.499
instruments[5622:274330] WebKit Threading Violation - initial use of
WebKit from a secondary thread.

Please help me out here ...

Screen Shot 2015-10-08 at 11.16.48 AM.png1370x1098 251 KB

congthang1
Oct '15

I got an error 

Error: connect ECONNREFUSED

when changing from appium 1.4.8 to 1.5 beta? I used session override.
Is that an issue or I need to add some other setting?

AndrewE
Oct '15

Hello!
I too am getting the following error when trying 1.5 via source. I am running appium by typing: node .

Error: Cannot find module '/Users/Andrew/appium/build/lib/main.js'
at Function.Module._resolveFilename (module.js:336:15)
at Function.Module._load (module.js:286:25)
at Function.Module.runMain (module.js:475:10)
at startup (node.js:118:18)
at node.js:952:3

AndrewE
Oct '15

Hello,
I saw this warning:
package.json appium@1.5.0-beta7 No bin file found at ./build/lib/main.js

So, I changed the package.json file to remove the 'build' directory for:
"main": "./lib/main.js",
"bin": {
"appium": "./lib/main.js",

Not sure if this was the right thing to do. I got past the first error but then have this one:
/Users/Andrew/appium/lib/main.js:4
import { init as logsinkInit } from './logsink';
^^^^^^

SyntaxError: Unexpected reserved word
at exports.runInThisContext (vm.js:53:16)
at Module._compile (module.js:414:25)
at Object.Module._extensions..js (module.js:442:10)
at Module.load (module.js:356:32)
at Function.Module._load (module.js:311:12)
at Function.Module.runMain (module.js:467:10)
at startup (node.js:134:18)
at node.js:961:3

isaac
Oct '15
AndrewE

I apologize. A missed step. Try running gulp transpile after you npm install.

AndrewE
Oct '15
isaac

Hi Isaac,
That worked perfectly, thanks! Needed to install gulp by running npm install -g gulp