This site is in read only mode. Please continue to browse, but replying, likes, and other actions are disabled for now.
8 / 42
Sep 2015

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?

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

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

node $APPIUM_BIN/appium.js

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

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

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

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.

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

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

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

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?

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

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

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

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

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.

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