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.

cannot spawn openssl

See original GitHub issue

🐛 Bug Report

Installed flipper, it doesn’t connect to my app/simulator, I assume it’s because of this error:

I tried installing Watchman fresh from brew which watchman returns /usr/local/bin/watchman

To Reproduce

Install flipper Try to use it?

Environment

macOS 11.5.2 Flipper 0.105.0 (on desktop and in react native app)

Sorry if I missed something obvious 😬

Issue Analytics

State:
Created 2 years ago
Reactions:1
Comments:9 (3 by maintainers)

Top GitHub Comments

4reactions

Moises-dev08commented, Dec 28, 2021

My problem resolved with this command in powershell:

choco install openssl

1reaction

mweststratecommented, Dec 29, 2021

I’ll add an error to make sure the absence of openSSL during startup is more clearly communicated

Top Results From Across the Web

How to respond to openssl prompts in nodejs - Stack Overflow

You need to use child_process.spawn , and then forward its stdin and stdout through your Node script using { stdio: "inherit" } ....

Solved: Re: Can't run openssl through Node (using execFile...

Hi,. I'm having difficulty accessing openssl through node on Cloud Run. The error is: Error: spawn openssl ENOENT. The (simplified code is).

1950018 – Cannot install npm package from github

I think I've found another similar issue due to packages that were removed. The OpenSSL headers no longer seem to be present so...

git-askpass.exe: No such file or directory

cannot spawn /C/Program Files (x86)/Microsoft Visual ... file:C:/Program Files/Git/mingw64/etc/gitconfig http.sslbackend=openssl file:C:/Program ...

spawn node ENOENT" when using child_process in Node.js

The reason the spawn was broken in the first place was because we were overriding the child process' environment variables in options.env which ......