Appium 1.5 Beta Release

isaac · Sep '15

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

Appium_Master · Oct '15

How to install appium 1.5 on windows 8 machine ?

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 ...

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

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

isaac · Oct '15

Can you provide more information about what you did?

AndrewE · Oct '15

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

rkrisztian1 · Oct '15

I can't get past this issue that I always fail to install appium-chromedriver:

> appium-chromedriver@2.3.5 install /home/rkrisztian1/tmp/appium-beta/appium-1.5/node_modules/appium-chromedriver
> node install-npm.js


/home/rkrisztian1/tmp/appium-beta/appium-1.5/node_modules/bluebird/js/main/promisify.js:268
        throw new TypeError("fn must be a function\u000a\u000a    See http://goo.gl/916lJJ\u000a");
              ^
TypeError: fn must be a function

    See http://goo.gl/916lJJ

    at Function.Promise.promisify (/home/rkrisztian1/tmp/appium-beta/appium-1.5/node_modules/bluebird/js/main/promisify.js:268:15)

Doesn't matter if I run it from a checkout with the mentioned npm install appium-chromedriver trick or via npm install appium@beta (without the checkout). It always fails.

isaac · Oct '15

Can you install appium-chromedriver on its own? If you go into a clean directory and run npm install appium-chromedriver what happens?

hemche · Oct '15

Hello @isaac ! Thanks for Shaping up Appium to be more reliable.

The appium@beta install is getting failed with below error related to appium chrome driver. Could you please suggest if something needs to get fixed from my side to get the latest appium 1.5 beta 7 installed ?

npm ERR! Darwin 14.5.0
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" "-g" "appium@beta" "--verbose"
npm ERR! node v4.1.0
npm ERR! npm  v2.14.4
npm ERR! code ELIFECYCLE

npm ERR! appium-chromedriver@2.3.8 install: `node install-npm.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the appium-chromedriver@2.3.8 install script 'node install-npm.js'.
npm ERR! This is most likely a problem with the appium-chromedriver package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node install-npm.js
npm ERR! You can get their info via:
npm ERR!     npm owner ls appium-chromedriver
npm ERR! There is likely additional logging output above.

Dhiren_Mudgil · Jan '16

Hi,

Getting this error when try to run appium.

/usr/lib/node_modules/appium/node_modules/bluebird/js/main/promisify.js:268
throw new TypeError("fn must be a function\u000a\u000a See http://goo.gl/916lJJ\u000a");
^
TypeError: fn must be a function

See http://goo.gl/916lJJ

at Function.Promise.promisify (/usr/lib/node_modules/appium/node_modules/bluebird/js/main/promisify.js:268:15)
at Object.<anonymous> (lib/fs.js:46:13)
at Module._compile (module.js:456:26)
at Object.Module._extensions..js (module.js:474:10)
at Module.load (module.js:356:32)
at Function.Module._load (module.js:312:12)
at Module.require (module.js:364:17)
at require (module.js:380:17)
at Object.<anonymous> (/usr/lib/node_modules/appium/node_modules/appium-support/build/lib/tempdir.js:12:11)
at Module._compile (module.js:456:26)
at Object.Module._extensions..js (module.js:474:10)
at Module.load (module.js:356:32)
at Function.Module._load (module.js:312:12)
at Module.require (module.js:364:17)
at require (module.js:380:17)
at Object.<anonymous> (/usr/lib/node_modules/appium/node_modules/appium-support/build/index.js:11:19)

rompic · Jan '16

i think you have to update your node version. which one are you using?

Dhiren_Mudgil · Jan '16

My node version is v0.10.25

My npm version is 1.3.10

rompic · Jan '16

see the discussion in https://github.com/appium/appium/issues/5814206

Dhiren_Mudgil · Jan '16

Thanks, Problem solved.

Tree · Jan '16

Hi, I have been using appium 1.4.16 successfully with android and ios, on both simulators and real devices. And have just tried using the 1.5 beta 9 but I get all sorts of problems. I'm hoping i've just missed some setup steps needed to use the 1.5 version of appium. I'm installing via 'npm install -g appium@1.5.0-beta9'

For IOS
I could not run on simulator (using same capabilities as used for 1.4.16). I have found this was due to having the capability fullReset: true. Seems it was deleting the simulator before the test and then not recreating it so the device was unable to be found for the test. Removing the capability resolved this problem(I also needed to recreate the simulator versions manually through the simulators manage devices option).

I could not run on a real device until I reinstalled ideviceinstaller through brew.
I am using xcode 7.1 and ios simulator 9.1

For Android
I cannot get it to find my app which is hosted on a local network (http://myaddress/android.apk).

[Selendroid] Error: Could not find app apk at 'http://myaddress/android.apk' at Object.wrappedLogger.errorAndThrow (lib/logger.js:60:13) at SelendroidDriver.checkAppPresent$ (lib/driver.js:226:14) at tryCatch (/usr/local/lib/node_modules/appium/node_modules/babel-runtime/regenerator/runtime.js:67:40) at GeneratorFunctionPrototype.invoke [as _invoke] (/usr/local/lib/node_modules/appium/node_modules/babel-runtime/regenerator/runtime.js:315:22) at GeneratorFunctionPrototype.prototype.(anonymous function) [as next] (/usr/local/lib/node_modules/appium/node_modules/babel-runtime/regenerator/runtime.js:100:21) at GeneratorFunctionPrototype.invoke (/usr/local/lib/node_modules/appium/node_modules/babel-runtime/regenerator/runtime.js:136:37) at run (/usr/local/lib/node_modules/appium/node_modules/core-js/library/modules/es6.promise.js:104:47) at /usr/local/lib/node_modules/appium/node_modules/core-js/library/modules/es6.promise.js:115:28 at flush (/usr/local/lib/node_modules/appium/node_modules/core-js/library/modules/$.microtask.js:19:5) at nextTickCallbackWith0Args (node.js:433:9) at process._tickCallback (node.js:362:13) [Error: Could not find app apk at 'http://myaddress/android.apk'] [debug] [Selendroid] Deleting Selendroid session

If I switch to a local copy for the app it then moves to a different error. Where it cannot find the android sdk's build-tools folder. It is looking for '...android-sdk/build-tools', however my sdk's build folder is at '...android-sdk/24.4.1_1/build-tools'

[MJSONWP] Calling AppiumDriver.createSession() with args: [{"appPackage":"nz.co.mcom.phone","appActivity":".activities.MobilitiActivity","platformName":"Android","automationName":"Selendroid","autoAcceptAl...
[Appium] Creating new SelendroidDriver session
[BaseDriver] The following capabilities were provided, but are not recognized by appium: autoAcceptAlerts, deviceType.
[BaseDriver] Session created with session id: 54336238-2655-4cdb-a335-88b914dc1533
[debug] [Selendroid] Checking whether app is actually present
[debug] [AndroidDriver] Getting Java version
[AndroidDriver] Java version is: 1.8.0_45
[ADB] Checking whether adb is present
[debug] [Selendroid] Deleting Selendroid session
[MJSONWP] Encountered internal error running command: Error: ENOENT: no such file or directory, scandir '/usr/local/Cellar/android-sdk/build-tools'
at Error (native)

note: the same error occurs if I use automationName: Appium, instead of Selendroid.
EDIT: rolling back to 1.4.16 did not resolve sdk issues this time. Seems like my Android SDK is messed up. So just the network url for the app path that is an issue for Android it seems. And perhaps that is an issue with Selendroid 0.17 since it doesent happen with Appium as the AutomatinoName

Any thoughts on how to resolve these issues? need me to provide more logging?

VikramVI · Feb '16

@isaac Today had removed appium version 1.4.16 ( installed though npm ) and installed beta version as per your post.

I couple of doubts wrt it

appium@1.5.0-beta16 but in github it shows https://github.com/appium/appium/releases10 1.5.0-beta12 ,why is the difference ?
npm list --global shows below messages

npm ERR! missing: appium-ios-simulator@^1.4.0, required by appium-instruments@3.6.0
npm ERR! missing: appium-logger@^2.1.0, required by appium-instruments@3.6.0
npm ERR! missing: appium-support@^2.0.9, required by appium-instruments@3.6.0

How to fix these ?

Thanks,
Vikram

isaac · Feb '16

1) Because as bugs are found and fixed there have been new releases, and whoever did the release was not necessarily good about tagging it as a release. But you want the most recent one (as of this moment, beta 16).

2) I think this is probably due to some holdover from a previous install. You may need to remove the old appium installation (wherever Appium has been installed) and reinstall the beta. Sometimes npm misses things.

share a link to this topic