-
-
Notifications
You must be signed in to change notification settings - Fork 75
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error: Unable to build Espresso server - spawn ./gradlew ENOENT #763
Comments
What about lower NodeJS versions? |
One of my colleague is using the same Node version with me and he has the same issue. Another colleague who uses Node v14.x doesn't have this issue though. |
interesting... anyway, the 2) full path is reasonable way. I've created a pr to make it full path. |
espresso driver 2.2.1 has the 2). |
I'm still encoutering the same error using 2.2.1 on an M1 Mac using the appium boilerplate project. This is the config I am using:
` I've tried this with appium and the espresso driver installed globally and locally, and with Node 16 and 17 and get the error but with no additional information as to why. If I browse into the module folder and run |
Could you share the full appium log as GIST? |
https://gist.github.com/JasonSznol/34da273696d1e56c36403485f88db024 |
Do you have the appium server instead of webdriverio's log? |
I was able to resolve the issue, turns out NPM was resolving a very old version of the driver. Sorry about that! |
@JasonSznol how did you solve it, i am getting this error and not able to resolve it. Tried real devices as well as emulator [debug] [ADB] Removing forwarded port socket connection: 8300 |
@psangwan8 In my case when I ran |
Hi when I try to run the espresso server I got the ENOENT error.
Logs
It looks like it failed when spawning the subprocess to run
./gradlew
but the command was executed successfully.Environment
System: macOS Monterey Version 12.3.1
Node: v17.8.0
Appium: v1.22.3
Appium-Epsresso-Driver: v2.2.0
Workarounds found
shell: true
in the options passed to create theSubProcess
instance inserver-builder.js
,runBuildProcess
function:With this it seems the error is gone.
2. Changing the command to
`${this.serverPath}/gradlew`
instead of./gradlew
onlyI wonder if it's just my environment issue. I also tried to run a separate file using Node's child_process's spawn function and it also fails with ENOENT:
Again, uncommenting
// shell: true
will also fix the issueThe text was updated successfully, but these errors were encountered: