Giter Site home page Giter Site logo

appium-doctor's Introduction

Deprecated

Please refer to https://github.com/appium/appium/tree/master/packages/doctor

appium-doctor

Attempts to diagnose and fix common Node, iOS and Android configuration issues before starting Appium.

Build Status

Install

npm install appium-doctor -g

Usage

➜  appium-doctor -h

Usage: appium-doctor.js [options, defaults: --ios --android]

Options:
  --ios       Check iOS setup                             [boolean]
  --android   Check Android setup                         [boolean]
  --dev       Check dev setup                             [boolean]
  --debug     Show debug messages                         [boolean]
  --yes       Always respond yes                          [boolean]
  --no        Always respond no                           [boolean]
  --demo      Run appium-doctor demo (for dev).           [boolean]
  -h, --help  Show help                                   [boolean]

Dev

Watch

npm run watch

Test

npm test

Hack Cli

Use the --demo option to simulate the fix process.

appium-doctor --demo

appium-doctor's People

Contributors

deep9 avatar dependabot-preview[bot] avatar dependabot[bot] avatar dpgraham avatar greenkeeper[bot] avatar imurchie avatar jlipps avatar kazucocoa avatar kelset avatar ltpquang avatar mykola-mokhnach avatar pinealan avatar sa-spag avatar scottdixon avatar sebv avatar wluu avatar wmaiouiru avatar zcmgyu avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

appium-doctor's Issues

Error after upgrading to MacOS High Sierra

When running Appium doctor, in MacOS High Sierra I am getting the following error:

Could not detect Mac OS X Version from sw_vers output: '10.13' at Object.macOsxVersion$ (/usr/local/lib/node_modules/appium-doctor/node_modules/appium-support/build/lib/system.js:114:15) at tryCatch (/usr/local/lib/node_modules/appium-doctor/node_modules/babel-runtime/regenerator/runtime.js:67:40) at GeneratorFunctionPrototype.invoke [as _invoke] (/usr/local/lib/node_modules/appium-doctor/node_modules/babel-runtime/regenerator/runtime.js:315:22) at GeneratorFunctionPrototype.prototype.(anonymous function) [as next] (/usr/local/lib/node_modules/appium-doctor/node_modules/babel-runtime/regenerator/runtime.js:100:21) at GeneratorFunctionPrototype.invoke (/usr/local/lib/node_modules/appium-doctor/node_modules/babel-runtime/regenerator/runtime.js:136:37) at <anonymous> at process._tickCallback (internal/process/next_tick.js:188:7)

appium-doctor Error report in execution 如何解决 How to solve this problem

C:\Users\Administrator>appium-doctor

C:\Users\Administrator\AppData\Roaming\npm\node_modules\appium-doctor\node_modules_bluebird@3.7.2@bluebird\js\release\promisify.js:270
throw new TypeError("expecting a function but got " + util.classString(fn));
^
TypeError: expecting a function but got [object Undefined]
at Function.promisify (C:\Users\Administrator\AppData\Roaming\npm\node_modules\appium-doctor\node_modules_bluebird@3.7.2@bluebird\js\release\promisify.js:270:15)
at Object. (C:\Users\Administrator\AppData\Roaming\npm\node_modules\appium-doctor\node_modules_appium-support@2.48.1@appium-support\lib\zip.js:17:20)
at Module._compile (module.js:653:30)
at Object.Module._extensions..js (module.js:664:10)
at Module.load (module.js:566:32)
at tryModuleLoad (module.js:506:12)
at Function.Module._load (module.js:498:3)
at Module.require (module.js:597:17)
at require (internal/module.js:11:18)
at Object. (C:\Users\Administrator\AppData\Roaming\npm\node_modules\appium-doctor\node_modules_appium-support@2.48.1@appium-support\index.js:10:1)
at Module._compile (module.js:653:30)
at Object.Module._extensions..js (module.js:664:10)
at Module.load (module.js:566:32)
at tryModuleLoad (module.js:506:12)
at Function.Module._load (module.js:498:3)
at Module.require (module.js:597:17)

opencv4nodejs not exist while appium-doctor passes

From Appium Log:
2020-07-12 08:58:13:274 [Support] Initializing opencv
2020-07-12 08:58:13:274 [Support] Loading local package 'opencv4nodejs'
2020-07-12 08:58:15:138 [Support] Failed to load local package 'opencv4nodejs': The module '/usr/local/lib/node_modules/opencv4nodejs/build/Release/opencv4nodejs.node'
2020-07-12 08:58:15:138 [Support] was compiled against a different Node.js version using
2020-07-12 08:58:15:138 [Support] NODE_MODULE_VERSION 64. This version of Node.js requires
2020-07-12 08:58:15:139 [Support] NODE_MODULE_VERSION 72. Please try re-compiling or re-installing
2020-07-12 08:58:15:139 [Support] the module (for instance, using npm rebuild or npm install).
2020-07-12 08:58:15:173 [Support] Failed to load global package 'opencv4nodejs': The "path" argument must be of type string. Received undefined
2020-07-12 08:58:15:173 [Support] Linking package 'opencv4nodejs'
2020-07-12 08:58:15:680 [Support] Retrying load of linked package 'opencv4nodejs'
2020-07-12 08:58:15:683 [Support] Unable to load package 'opencv4nodejs': Module did not self-register: '/usr/local/lib/node_modules/opencv4nodejs/build/Release/opencv4nodejs.node'.
2020-07-12 08:58:15:683 [Support] Unable to load 'opencv4nodejs': Unable to load package 'opencv4nodejs': Module did not self-register: '/usr/local/lib/node_modules/opencv4nodejs/build/Release/opencv4nodejs.node'.
2020-07-12 08:58:15:684 [W3C (3d97b46b)] Encountered internal error running command: Error: 'opencv4nodejs' module is required to use OpenCV features. Please install it first ('npm i -g opencv4nodejs') and restart Appium. Read https://github.com/justadudewhohacks/opencv4nodejs#how-to-install for more details on this topic.
2020-07-12 08:58:15:684 [W3C (3d97b46b)] at initOpenCV (/usr/local/lib/node_modules/appium/node_modules/appium-support/lib/image-util.js:109:11)

From appium-doctor log:
info AppiumDoctor Appium Doctor v.1.15.3
info AppiumDoctor ### Diagnostic for necessary dependencies starting ###
info AppiumDoctor ✔ The Node.js binary was found at: /usr/local/bin/node
info AppiumDoctor ✔ Node version is 12.18.2
info AppiumDoctor ✔ Xcode is installed at: /Applications/Xcode.app/Contents/Developer
info AppiumDoctor ✔ Xcode Command Line Tools are installed in: /Applications/Xcode.app/Contents/Developer
info AppiumDoctor ✔ DevToolsSecurity is enabled.
info AppiumDoctor ✔ The Authorization DB is set up properly.
info AppiumDoctor ✔ Carthage was found at: /usr/local/bin/carthage. Installed version is: 0.33.0
info AppiumDoctor ✔ HOME is set to: /Users/cellactqa
info AppiumDoctor ✔ ANDROID_HOME is set to: /Users/cellactqa/Library/Android/sdk
info AppiumDoctor ✔ JAVA_HOME is set to: /Library/Java/JavaVirtualMachines/jdk1.8.0_141.jdk/Contents/Home
info AppiumDoctor Checking adb, android, emulator
info AppiumDoctor 'adb' is in /Users/cellactqa/Library/Android/sdk/platform-tools/adb
info AppiumDoctor 'android' is in /Users/cellactqa/Library/Android/sdk/tools/android
info AppiumDoctor 'emulator' is in /Users/cellactqa/Library/Android/sdk/emulator/emulator
info AppiumDoctor ✔ adb, android, emulator exist: /Users/cellactqa/Library/Android/sdk
info AppiumDoctor ✔ Bin directory of $JAVA_HOME is set
info AppiumDoctor ### Diagnostic for necessary dependencies completed, no fix needed. ###
info AppiumDoctor
info AppiumDoctor ### Diagnostic for optional dependencies starting ###
info AppiumDoctor ✔ opencv4nodejs is installed at: /usr/local/lib. Installed version is: 5.6.0
info AppiumDoctor ✔ ffmpeg is installed at: /usr/local/bin/ffmpeg. ffmpeg version 4.3.1 Copyright (c) 2000-2020 the FFmpeg developers
info AppiumDoctor ✔ mjpeg-consumer is installed at: /usr/local/lib. Installed version is: 2.0.0
info AppiumDoctor ✔ set-simulator-location is installed
info AppiumDoctor ✔ idb and idb_companion are installed
info AppiumDoctor ✔ applesimutils is installed at: /usr/local/bin/applesimutils. Installed versions are: applesimutils 0.7.2
info AppiumDoctor ✔ ios-deploy is installed at: /usr/local/bin/ios-deploy. Installed version is: 1.9.4
info AppiumDoctor ✔ bundletool.jar is installed at: /Users/cellactqa/Library/Android/sdk/platform-tools/bundletool.jar
info AppiumDoctor ✔ gst-launch-1.0 and gst-inspect-1.0 are installed at: /usr/local/bin/gst-launch-1.0 and /usr/local/bin/gst-inspect-1.0
info AppiumDoctor ### Diagnostic for optional dependencies completed, no fix possible. ###
info AppiumDoctor
info AppiumDoctor Everything looks good, bye!
info AppiumDoctor

Use -j option to compare npm module versions

npm ls -g -j mjpeg-consumer

$ npm ls -g -j mjpeg-consumer
{
  "dependencies": {
    "mjpeg-consumer": {
      "version": "1.1.0",
      "from": "mjpeg-consumer",
      "resolved": "https://registry.npmjs.org/mjpeg-consumer/-/mjpeg-consumer-1.1.0.tgz"
    }
  }
}

$ npm ls -g -j something-non-existent
{}

for opencv4nodejs and mjpeg-consumer

An in-range update of appium-support is breaking the build 🚨

Version 2.18.0 of appium-support was just published.

Branch Build failing 🚨
Dependency appium-support
Current Version 2.17.0
Type dependency

This version is covered by your current version range and after updating it in your project the build failed.

appium-support is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details
  • continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

Commits

The new version differs by 4 commits.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

Running Doctor from Appium.app could not detect Mac OS X Version

Output:

info AppiumDoctor ### Diagnostic starting ###
info AppiumDoctor  ✔ Xcode is installed at: /Applications/Xcode.app/Contents/Developer
[Error: Could not detect Mac OS X Version from sw_vers output: '10.12.3
']

Is this something that could cause issues elsewhere?

[MJSONWP] Encountered internal error running command: Error: '10.13.3' does not exist in the list of simctl SDKs. Only the following Simulator SDK versions are available on your system: 11.2

Hi,
I have tried to Run Appium on my mac , getting this error , could you please tell me the solution.

My Jason File : {
"platformName": "iOS",
"platformVersion": "10.13.3",
"deviceName": "SabyaSanchi's iPhone",
"Udid": "7ec7d8cfab5160bd240b28a10e4aae8770fb59c9",
"app": "/Users/smishra/Desktop/IntegrationApp.app"

Appium 1.5 doctor display xcode info in Win

I have already update appium to 1.5

In win10, run appium-doctor in terminal and display appium-doctor command not found.

Then npm install appium-doctor -g and run again, but display

info AppiumDoctor ### Diagnostic starting ###
WARN AppiumDoctor x Xcode is Not installed!

but my platform is Win10.

An in-range update of bluebird is breaking the build 🚨

The dependency bluebird was updated from 3.5.2 to 3.5.3.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

bluebird is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details
  • continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

Release Notes for v3.5.3

Bugfixes:

  • Update acorn dependency
Commits

The new version differs by 7 commits.

  • a5a5b57 Release v3.5.3
  • c8a7714 update packagelock
  • 8a765fd Update getting-started.md (#1561)
  • f541801 deps: update acorn and add acorn-walk (#1560)
  • 247e512 Update promise.each.md (#1555)
  • e2756e5 fixed browser cdn links (#1554)
  • 7cfa9f7 Changed expected behaviour when promisifying (#1545)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

1.16.1 was broken

Issue.

yarn doctor
yarn run v1.22.18
warning package.json: No license field
$ appium-doctor --ios
node:internal/modules/cjs/loader:936
  throw err;
  ^

Error: Cannot find module './build/bin/appium-doctor'
Require stack:
- /Users/bill/theclub/TheClub/browserstack/node_modules/appium-doctor/appium-doctor.js
    at Function.Module._resolveFilename (node:internal/modules/cjs/loader:933:15)
    at Function.Module._load (node:internal/modules/cjs/loader:778:27)
    at Module.require (node:internal/modules/cjs/loader:1005:19)
    at require (node:internal/modules/cjs/helpers:102:18)
    at Object.<anonymous> (/Users/bill/theclub/TheClub/browserstack/node_modules/appium-doctor/appium-doctor.js:3:1)
    at Module._compile (node:internal/modules/cjs/loader:1105:14)
    at Object.Module._extensions..js (node:internal/modules/cjs/loader:1159:10)
    at Module.load (node:internal/modules/cjs/loader:981:32)
    at Function.Module._load (node:internal/modules/cjs/loader:822:12)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:77:12) {
  code: 'MODULE_NOT_FOUND',
  requireStack: [
    '/Users/bill/theclub/TheClub/browserstack/node_modules/appium-doctor/appium-doctor.js'
  ]
}
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

Issue with finding mjpeg-consumer

Warning:

w-cr8:~ cellactqa$ npm ls -g -j mjpeg-consumer
{
  "dependencies": {
    "appium": {
      "version": "1.15.1",
      "from": "appium",
      "resolved": "https://registry.npmjs.org/appium/-/appium-1.15.1.tgz",
      "dependencies": {
        "appium-xcuitest-driver": {
          "version": "2.133.1",
          "from": "[email protected]",
          "resolved": "https://registry.npmjs.org/appium-xcuitest-driver/-/appium-xcuitest-driver-2.133.1.tgz",
          "dependencies": {
            "mjpeg-consumer": {
              "version": "2.0.0",
              "from": "mjpeg-consumer",
              "resolved": "https://registry.npmjs.org/mjpeg-consumer/-/mjpeg-consumer-2.0.0.tgz"
            }
          }
        }
      }
    }
  }
}
w-cr8:~ cellactqa$ 
w-cr8:~ cellactqa$ 
w-cr8:~ cellactqa$ 
w-cr8:~ cellactqa$ appium-doctor
info AppiumDoctor Appium Doctor v.1.12.1
info AppiumDoctor ### Diagnostic for necessary dependencies starting ###
info AppiumDoctor  ✔ The Node.js binary was found at: /usr/local/bin/node
info AppiumDoctor  ✔ Node version is 10.16.3
info AppiumDoctor  ✔ Xcode is installed at: /Applications/Xcode.app/Contents/Developer
info AppiumDoctor  ✔ Xcode Command Line Tools are installed in: /Applications/Xcode.app/Contents/Developer
info AppiumDoctor  ✔ DevToolsSecurity is enabled.
info AppiumDoctor  ✔ The Authorization DB is set up properly.
info AppiumDoctor  ✔ Carthage was found at: /usr/local/bin/carthage. Installed version is: 0.33.0
info AppiumDoctor  ✔ HOME is set to: /Users/cellactqa
info AppiumDoctor  ✔ ANDROID_HOME is set to: /Users/cellactqa/Library/Android/sdk
info AppiumDoctor  ✔ JAVA_HOME is set to: /Library/Java/JavaVirtualMachines/jdk1.8.0_192.jdk/Contents/Home
info AppiumDoctor  ✔ adb exists at: /Users/cellactqa/Library/Android/sdk/platform-tools/adb
info AppiumDoctor  ✔ android exists at: /Users/cellactqa/Library/Android/sdk/tools/android
info AppiumDoctor  ✔ emulator exists at: /Users/cellactqa/Library/Android/sdk/tools/emulator
info AppiumDoctor  ✔ Bin directory of $JAVA_HOME is set
info AppiumDoctor ### Diagnostic for necessary dependencies completed, no fix needed. ###
info AppiumDoctor 
info AppiumDoctor ### Diagnostic for optional dependencies starting ###
info AppiumDoctor  ✔ opencv4nodejs is installed at: /usr/local/lib. Installed version is: 5.4.0
info AppiumDoctor  ✔ ffmpeg is installed at: /usr/local/bin/ffmpeg. ffmpeg version 4.2.1 Copyright (c) 2000-2019 the FFmpeg developers
WARN AppiumDoctor  ✖ mjpeg-consumer cannot be found.
info AppiumDoctor  ✔ idb and idb_companion are installed
info AppiumDoctor  ✔ applesimutils is installed at: /usr/local/bin/applesimutils. Installed versions are: applesimutils 0.7.2
info AppiumDoctor  ✔ bundletool.jar is installed at: /Users/cellactqa/Library/Android/sdk/build-tools/bundletool.jar
info AppiumDoctor ### Diagnostic for optional dependencies completed, one fix possible. ###
info AppiumDoctor 
info AppiumDoctor ### Optional Manual Fixes ###
info AppiumDoctor The configuration can install optionally. Please do the following manually:
WARN AppiumDoctor  ➜ mjpeg-consumer module is required to use MJPEG-over-HTTP features. Please install it with 'npm i -g mjpeg-consumer'.
info AppiumDoctor 
info AppiumDoctor ###
info AppiumDoctor 
info AppiumDoctor Bye! Run appium-doctor again when all manual fixes have been applied!

Can not be executed on Windows 10

OS: Windows 10 Pro

Since I'm not a big fan of -g installs, I've created an empty npm project, and installed appium-doctor using
npm install --save appium appium-doctor

Then by adding appium-doctor in scripts section of package.json I'm able to execute.

But receiving this error:

TypeError: Cannot read property 'replace' of undefined
    at Function.retrieveUsingWhichCommand$ (X:\ondra\internal\appium-test\node_modules\appium-doctor\build\lib\node-detector.js:152:30)
    at tryCatch (X:\ondra\internal\appium-test\node_modules\babel-runtime\regenerator\runtime.js:67:40)
    at GeneratorFunctionPrototype.invoke [as _invoke] (X:\ondra\internal\appium-test\node_modules\babel-runtime\regenerator\runtime.js:315:22)
    at GeneratorFunctionPrototype.prototype.(anonymous function) [as throw] (X:\ondra\internal\appium-test\node_modules\babel-runtime\regenerator\runtime.js:100:21)
    at GeneratorFunctionPrototype.invoke (X:\ondra\internal\appium-test\node_modules\babel-runtime\regenerator\runtime.js:136:37)
    at process._tickCallback (internal/process/next_tick.js:103:7)

npm ERR! Windows_NT 10.0.14393
npm ERR! argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "run" "appium-doctor"
npm ERR! node v6.9.2
npm ERR! npm  v3.10.9
npm ERR! code ELIFECYCLE
npm ERR! [email protected] appium-doctor: `appium-doctor`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] appium-doctor script 'appium-doctor'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the appium-test package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     appium-doctor
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs appium-test
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls appium-test
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     \appium-test\npm-debug.log

Looking in the code I've noticed you can set NODE_BIN variable to skip all the automatic lookups for a node. It might be stated in the readme, as recommended on Windows.

There is also a one-liner to set the variable using Windows' where:
for /f "delims==" %i in ('where node') do @set "NODE_BIN=%i"

Update required node version to 10+

async diagnose () {
let nodePath = await NodeDetector.detect();
if (!nodePath) {
return nok('Node is not installed, so no version to check!');
}
let {stdout} = await exec(nodePath, ['--version']);
let versionString = stdout.replace('v', '').trim();
let version = parseInt(versionString, 10);
if (Number.isNaN(version)) {
return nok(`Unable to find node version (version = '${versionString}')`);
}
return version >= 4 ? ok(`Node version is ${versionString}`) :
nok('Node version should be at least 4!');
}

Current implementation is 4.

It will help users/us to notice to update their node version to 10+
(Especially 'path' error case)


will do soon

1.5 Cleanup

  • Make sure all deps are up to date (and there are no unused deps)
  • Take a look at all TODOs to see if we need to resolve any for the release
  • Set up code coverage
  • Set up CI (unit tests, functional tests, code coverage; should be on all relevant platforms, and should include multi-executor parallelism for long-running testsuites)
  • Ensure that we are using appium-support functions, not home-grown helpers
  • Ensure that we have high unit test code coverage percentage
  • Ensure that we have sufficient/appropriate functional test coverage
  • Write a decent README, explaining (a) what the purpose of the module is, (b) how it relates to other appium modules, and (c) how to use its interface
  • Ensure that code conforms to our style
  • Ensure we are not using any sync functions
  • Ensure that code is well-commented
  • Ensure that non-production code or assets are added to .npmignore to reduce npm install size

appium-doctor break off on mac

Warning:

These issues are not tracked. Please create new issues in the main Appium
repository: https://github.com/appium/appium/issues/new

Mac 10.14.4

node -v
v12.1.0
npm -v
6.9.0
appium -v
1.13.0

~$appium-doctor
info AppiumDoctor Appium Doctor v.1.10.0
info AppiumDoctor ### Diagnostic for necessary dependencies starting ###
info AppiumDoctor ✔ The Node.js binary was found at: /usr/local/bin/node
info AppiumDoctor ✔ Node version is 12.1.0

appim-doctor not working

Hello,
I'm trying run appium doctor but the error below happens.
Someone can help?

macOS Mojave: 10.14.6
sh-3.2# npm -v
6.13.4
sh-3.2# node -v
v12.14.1
sh-3.2# appium-doctor
info AppiumDoctor Appium Doctor v.1.13.0
info AppiumDoctor ### Diagnostic for necessary dependencies starting ###
info AppiumDoctor ✔ The Node.js binary was found at: /usr/local/bin/node
info AppiumDoctor ✔ Node version is 12.14.1
Error: Command 'ffmpeg -version' exited with code null
at ChildProcess. (/usr/local/lib/node_modules/appium-doctor/node_modules/teen_process/lib/exec.js:113:19)
at ChildProcess.emit (events.js:223:5)
at maybeClose (internal/child_process.js:1021:16)
at Process.ChildProcess._handle.onexit (internal/child_process.js:283:5) {
stdout: '',
stderr: 'dyld: Library not loaded: /usr/local/opt/openssl/lib/libssl.1.0.0.dylib\n' +
' Referenced from: /usr/local/bin/ffmpeg\n' +
' Reason: image not found\n',
code: null
}
sh-3.2#

Action required: Greenkeeper could not be activated 🚨

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please delete the greenkeeper/initial branch in this repository, and then remove and re-add this repository to the Greenkeeper App’s white list on Github. You'll find this list on your repo or organization’s settings page, under Installed GitHub Apps.

How to set the JAVA_HOME/bin directory?

my .bash_profile file is
JAVA_HOME=$(/usr/libexec/java_home)
export JAVA_HOME
PATH=$PATH:$JAVA_HOME/bin
export PATH

but I run the 'appium-doctor --android' command, give me the failed tips for "JAVA_HOME/bin"
info AppiumDoctor ### Diagnostic starting ###
info AppiumDoctor ✔ ANDROID_HOME is set to: /Users/gaojiewen/android-sdk
info AppiumDoctor ✔ JAVA_HOME is set to: /Library/Java/JavaVirtualMachines/jdk1.8.0_102.jdk/Contents/Home
info AppiumDoctor ✔ adb exists at: /Users/gaojiewen/android-sdk/platform-tools/adb
info AppiumDoctor ✔ android exists at: /Users/gaojiewen/android-sdk/tools/android
info AppiumDoctor ✔ emulator exists at: /Users/gaojiewen/android-sdk/tools/emulator
WARN AppiumDoctor ✖ Bin directory of $JAVA_HOME is not set
info AppiumDoctor ### Diagnostic completed, one fix needed. ###
info AppiumDoctor
info AppiumDoctor ### Manual Fixes Needed ###
info AppiumDoctor The configuration cannot be automatically fixed, please do the following first:
WARN AppiumDoctor - Add '$JAVA_HOME/bin' to your PATH environment
info AppiumDoctor ###
info AppiumDoctor
info AppiumDoctor Bye, run appium-doctor again when all manual fixes have been applied!
info AppiumDoctor

Can't open appium doctor (node version: v8.16.2, macOS: Catalina)

Can you please help with this error:

/Users/andreecarreno/.nvm/versions/node/v8.16.2/lib/node_modules/appium-doctor/build/lib/general.js:59
} catch {
^

SyntaxError: Unexpected token {
at createScript (vm.js:80:10)
at Object.runInThisContext (vm.js:139:10)
at Module._compile (module.js:617:28)
at Object.Module._extensions..js (module.js:664:10)
at Module.load (module.js:566:32)
at tryModuleLoad (module.js:506:12)
at Function.Module._load (module.js:498:3)
at Module.require (module.js:597:17)
at require (internal/module.js:11:18)
at Object. (/Users/andreecarreno/.nvm/versions/node/v8.16.2/lib/node_modules/appium-doctor/lib/factory.js:3:1)
at Module._compile (module.js:653:30)
at Object.Module._extensions..js (module.js:664:10)
at Module.load (module.js:566:32)
at tryModuleLoad (module.js:506:12)
at Function.Module._load (module.js:498:3)
at Module.require (module.js:597:17)
at require (internal/module.js:11:18)
at Object. (/Users/andreecarreno/.nvm/versions/node/v8.16.2/lib/node_modules/appium-doctor/bin/appium-doctor.js:4:1)
at Module._compile (module.js:653:30)
at Object.Module._extensions..js (module.js:664:10)
at Module.load (module.js:566:32)
at tryModuleLoad (module.js:506:12)

(node version: v8.16.2, macOS: Catalina)

lint error

Will take a look later:

[19:46:09] Using gulpfile ~/GitHub/appium-doctor/gulpfile.js
[19:46:09] Starting 'lint'...
[19:46:09] Starting 'eslint'...
[19:46:12]
/Users/kazuaki/GitHub/appium-doctor/lib/android.js
  96:19  error  Parsing error: /Users/kazuaki/GitHub/appium-doctor/lib/android.js: Support for the experimental syntax 'classProperties' isn't currently enabled (96:20):

  94 |
  95 | class OptionalGstreamerCheck extends DoctorCheck {
> 96 |   GSTREAMER_BINARY = `gst-launch-1.0${system.isWindows() ? '.exe' : ''}`;
     |                    ^
  97 |   GST_INSPECT_BINARY = `gst-inspect-1.0${system.isWindows() ? '.exe' : ''}`;
  98 |
  99 |   async diagnose () {

Add @babel/plugin-proposal-class-properties (https://git.io/vb4SL) to the 'plugins' section of your Babel config to enable transformation.
If you want to leave it as-is, add @babel/plugin-syntax-class-properties (https://git.io/vb4yQ) to the 'plugins' section to enable parsing

When using NVM it doesn't detect node.exe

I use NVM for Windows for versioning nodejs. When running where node it spits out these values

$ where node

F:\Tools\nodejs\node.exe
C:\Program Files\nodejs\node.exe
C:\Program Files\Microsoft MPI\Bin\node.exe

It creates a symlink from C drive to F drive. I also have another binary called node.
And now we have a collision.
https://github.com/appium/appium-doctor/blob/master/lib/node-detector.js#L39.

let nodePath = stdout.replace(/[\n\r]/g, "");

Here we concatenate those paths, which results in this mess: F:\Tools\nodejs\node.exeC:\Program Files\nodejs\node.exeC:\Program Files\Microsoft MPI\Bin\node.exe.

Which the next line always returns false.

if (await fs.exists(nodePath)) {

And thus always failing to detect node

Allow package to be used as a module

Hey,

I would be interested to integrate appium-doctor into the WebdriverIO set-up wizard. For that I would love to make this tool consumable as a module so I can import and run it with arguments, e.g.:

import { check } from 'appium-doctor'

const result = await check(args)

Where result is an object with the results that allows one to print it somewhere or take own actions.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.