question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

TypeError: Path must be a string. Received undefined

See original GitHub issue

The problem

I am pretty much facing this issue: https://github.com/appium/appium/issues/6978 after upgrading appium. So I tried the solution from #6978
npm install -g appium --no-shrinkwrap and I got the following error when starting appium: TypeError: Path must be a string. Received undefined

How am I supposed to get it working?

Environment

  • appium@1.6.0
  • Windows 10
  • Real device or emulator/simulator: Emulator

Appium logs

C:\WINDOWS\system32>npm install -g appium --no-shrinkwrap npm WARN deprecated babel-core@5.8.24: Babel 5 is no longer being maintained. Upgrade to Babel 6. npm WARN deprecated minimatch@2.0.10: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue npm WARN deprecated line-numbers@0.2.0: Copy its ~20 LOC directly into your code instead. C:\Users\rafal\AppData\Roaming\npm\appium -> C:\Users\rafal\AppData\Roaming\npm\node_modules\appium\build\lib\main.js C:\Users\rafal\AppData\Roaming\npm `-- appium@1.6.0

npm WARN optional Skipping failed optional dependency /appium/fsevents: npm WARN notsup Not compatible with your operating system or architecture: fsevents@1.0.14

C:\WINDOWS\system32>appium TypeError: Path must be a string. Received undefined at assertPath (path.js:7:11) at Object.resolve (path.js:184:7) at Object.<anonymous> (lib/driver.js:45:8) at Module._compile (module.js:541:32)

Code To Reproduce Issue [ Good To Have ]

start appium from command line

Issue Analytics

  • State:closed
  • Created 7 years ago
  • Comments:12 (5 by maintainers)

github_iconTop GitHub Comments

1reaction
rafalfcommented, Oct 30, 2016

Closing it

1reaction
imurchiecommented, Oct 24, 2016

I don’t know. The command on line 16 is not getting to the server, for whatever reason.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Jest TypeError: Path must be a string. Received undefined
I solved this issue using: npm uninstall -g jest; npm install -g jest; npm cache clean; npm install.
Read more >
"Path must be a string. Received undefined" #144 - zkat/npx
Happy to try to help. The reason people all over www get 'Path must be a string' in Windows is because it it...
Read more >
path must be a string. received undefined when building a ...
I'm attempting to build a xamarin.ios project on a hosted agent. The project builds fine on a private agent we use, but in...
Read more >
Path must be a string. Received undefined - node-steam-user
Stack Trace: TypeError: Path must be a string. Received undefined at assertPath (path.js:28:11) at Object.join (path.js:489:7) at userData ...
Read more >
npm error: TypeError('Path must be a string. Received ... - Reddit
I'm using node.js version 6.9.1, and I can create classes just fine. But I can't use the new "import" word. I only get...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found