Skip to content
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

A problem occurred starting process 'command '..\..\node_modules\hermesvm\win64-bin\hermes'' #26072

Closed
valery-lavrik opened this issue Aug 15, 2019 · 15 comments
Labels
Bug Stale There has been a lack of activity on this issue and it may be closed soon. Tech: Hermes Hermes Engine: https://hermesengine.dev/

Comments

@valery-lavrik
Copy link

React Native version:
System:
OS: Windows 10
CPU: (4) x64 Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz
Memory: 2.00 GB / 7.49 GB
Binaries:
Node: 12.4.0 - C:\Program Files\nodejs\node.EXE
Yarn: 1.7.0 - C:\Program Files (x86)\Yarn\bin\yarn.CMD
npm: 6.9.0 - C:\Program Files\nodejs\npm.CMD
IDEs:
Android Studio: Version 3.4.0.0 AI-183.6156.11.34.5692245

Steps To Reproduce

1. cd android
2. ./gradlew clean
3. ./gradlew assembleRelease

**> Configure project :react-native-webview
:react-native-webview:reactNativeAndroidRoot E:\RN\st-react-native\node_modules\reactative\android

Task :app:bundleReleaseJsAndAssets
warn The following packages use deprecated "rnpm" config that will stop working from xt release:

Task :app:bundleReleaseJsAndAssets FAILED

FAILURE: Build failed with an exception.

  • What went wrong:
    Execution failed for task ':app:bundleReleaseJsAndAssets'.

A problem occurred starting process 'command '....\node_modules\hermesvm\win64-bin\hermes''

  • Try:
    Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

  • Get more help at https://help.gradle.org

Deprecated Gradle features were used in this build, making it incompatible with Gradle 6.0.
Use '--warning-mode all' to show the individual deprecation warnings.
See https://docs.gradle.org/5.4.1/userguide/command_line_interface.html#sec:command_line_warnings

BUILD FAILED in 2m 14s
65 actionable tasks: 59 executed, 6 up-to-date**


this happens with the latest updates:
image

and enableHermes: true

What should I do?

@radko93
Copy link
Contributor

radko93 commented Aug 15, 2019

Not sure if it's related, but React Native does not support React 16.9 yet

@valery-lavrik
Copy link
Author

@radko93 It's not related. The problem at the time of the operation of hermes. Therefore, I think the reaction itself is not to blame

@radko93
Copy link
Contributor

radko93 commented Aug 15, 2019

This should be set on project.ext.react and mirrored here. If it is not set on project.ext.react, JavaScript will not be compiled to Hermes Bytecode and the benefits of using Hermes will therefore be sharply reduced.

Did enable it as it's described here?

@valery-lavrik
Copy link
Author

@radko93 Yes of course
image

@sasclau
Copy link

sasclau commented Aug 17, 2019

Same problem on windows 10

@radko93 radko93 added the Tech: Hermes Hermes Engine: https://hermesengine.dev/ label Aug 19, 2019
@seriiix
Copy link

seriiix commented Aug 19, 2019

It's fine on mac but i have the same problem on win10

@PrimeObjects
Copy link

Got the same issue here

@hemmedo
Copy link

hemmedo commented Aug 22, 2019

Same here...isn't there any temporary workaround?

@gpawlik
Copy link

gpawlik commented Aug 22, 2019

@hemmedo please check where hermesvm has been installed within node_modules directory.

The default location is ../../node_modules/react-native/node_modules/hermesvm/%OS-BIN%/hermes but in my case it has been installed in the root of node_modules so I needed to reflect it in the gradle file like this:

project.ext.react = [
    ...some options...
    enableHermes: true,
    hermesCommand: "../../node_modules/hermesvm/%OS-BIN%/hermes"
]

@hemmedo
Copy link

hemmedo commented Aug 23, 2019

@gpawlik Although you were right about the path, it didn't change anything. Still getting the exact same error. Is this the only thing I have to do to make it work?

@gpawlik
Copy link

gpawlik commented Aug 23, 2019

@hemmedo Can you confirm that you have the same path when implementing hermes later on?

    if (enableHermes) {
        def hermesPath = "../../node_modules/hermesvm/android/";
        debugImplementation files(hermesPath + "hermes-debug.aar")
        releaseImplementation files(hermesPath + "hermes-release.aar")
    } else {
        implementation jscFlavor
    }

@andreasbergqvist
Copy link

My fix:
#25599 (comment)

@hemmedo
Copy link

hemmedo commented Aug 24, 2019

@gpawlik Fixed it. Turns out problem was really the execution of Hermes in windows so I just used that modified react.gradle for it.

@stale
Copy link

stale bot commented Nov 22, 2019

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. You may also label this issue as a "Discussion" or add it to the "Backlog" and I will leave it open. Thank you for your contributions.

@stale stale bot added the Stale There has been a lack of activity on this issue and it may be closed soon. label Nov 22, 2019
@stale
Copy link

stale bot commented Nov 29, 2019

Closing this issue after a prolonged period of inactivity. If this issue is still present in the latest release, please feel free to create a new issue with up-to-date information.

@stale stale bot closed this as completed Nov 29, 2019
@facebook facebook locked as resolved and limited conversation to collaborators Nov 30, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Bug Stale There has been a lack of activity on this issue and it may be closed soon. Tech: Hermes Hermes Engine: https://hermesengine.dev/
Projects
None yet
Development

No branches or pull requests

8 participants