-
Notifications
You must be signed in to change notification settings - Fork 24.4k
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
Hermes emit binary crash #25609
Comments
Hello @mjmasn , I face the same error. Do you have solution to generate signed apk with hermes engine without any errors ? |
@B4UGUYS see the last code snippet on this #25601 (comment) You'll need to copy react.gradle from node_modules to your android/app folder before editing it. Replace the line starting |
Thank you @mjmasn I was having the same issue, your snipped did the trick! |
For me, everything works locally but executing it on CI results in a reported error. Maybe memory issues with CI. Can Hermes memory usage, number of daemons/threads, can be limited? |
@mjmasn I also used your snippet and the problem was fixed, thanks! However, using the Android Studio APK Analyzer, I saw that a file called 'index.android.bundle_temp' is included in the assets directory. I guess this is related to your snippet. What can I do to fix this? |
@luckyluke19 hmm, good point, I haven't tried this but probably something like
after the hermes command? Let me know if that works and I'll update my post. I haven't really got time to look at any more switching-to-Hermes stuff in our app at the moment. |
@mjmasn No, it doesn't work. It shows the initial error again (Process 'command '../../node_modules/hermesvm/linux64-bin/hermes'' finished with non-zero exit value 135) |
@luckyluke19 you should move it outside |
@thinhtran3588 thanks, that worked! |
@reactjs-bot @react-native-bot @mjmasn i have followed the above steps but I get an error like this Process 'command '..\node_modules\hermesvm\win64-bin\hermes'' finished with non-zero exit value -1073741515 ` if (enableHermes) {
` |
./gradlew bundleRelease --info gave such a result:
How to enable cache? |
@valery-lavrik see my earlier comments #25601 (comment) NB this was a quick temporary workaround so I could test out Hermes, the RN / Hermes team need to fix this properly.
Below this (outside the exec section around
|
@mjmasn |
please anyone give solution about it. |
@mjmasn The solution to my problem is already in the last patch. c21e36d But during installation, an outdated version is installed for me. Why? |
@valery-lavrik this is because the commit you've linked is available in the latest master, but is not yet available in the stable releases. A new release containing this fix should be available soon enough. |
I think this issue is still on react native version 0.60.5 . |
@kashsbd I think so too |
yeah it still persists. |
In my case, the building release with --variant=release is working fine, but making bundle Release for play store is not working the application just crash immediately after the splash screen |
@adnkh Exactly the same thing happened to me. I uploaded APKs instead and the problem was fixed. |
@adnkh then why /gradlew assembleRelease isn't working? Technically they're doing the same thing. Nevertheless, I'm just gonna wait for this Hermes update to go live. |
Can I know how you fixed that?
…On Thu, Aug 22, 2019 at 3:19 PM LuckyLuke19 ***@***.***> wrote:
@adnkh <https://github.com/adnkh> Exactly the same thing happened to me.
I uploaded APKs instead and the problem was fixed.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#25609?email_source=notifications&email_token=AECTT6G4K4XM455RNSAWKITQFZOLNA5CNFSM4ICHH52KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD44QZSQ#issuecomment-523832522>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AECTT6CGQDKUFBEBGSFXG7LQFZOLNANCNFSM4ICHH52A>
.
--
Thanks and with regards,
* Nagaraj.R*
|
@nagaraj95 instead of running |
I ran this command only gradlew assembleRelease and got error like that
only
…On Thu, Aug 22, 2019 at 4:09 PM LuckyLuke19 ***@***.***> wrote:
@nagaraj95 <https://github.com/nagaraj95> instead of running ./gradlew
bundleRelease to generate an AAB file, I ran ./gradlew assembleRelease
and generated APK files. Is that what you mean?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#25609?email_source=notifications&email_token=AECTT6CMSXONJE3XBS6LW5DQFZUGLA5CNFSM4ICHH52KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD44UXFI#issuecomment-523848597>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AECTT6FYJK2BURHE4PLACZ3QFZUGLANCNFSM4ICHH52A>
.
--
Thanks and with regards,
* Nagaraj.R*
|
@luckyluke19 ./gradlew assembleRelease doesnt work for us. What did you do to get it working? |
@hemmedo, @nagaraj95 |
@zeljkoX same thing happens to me. Runs fine locally but crashes running on CircleCI. Did you find a fix? |
@aecorredor I haven't. |
I am still having this problem with |
having issue for 0.60.4 |
I follow you ,it‘s ok in 0.60.5 |
you did it in win10? |
Same error building with gitlab-ci, locally works perfectly, rn 0.60.5 |
@zeljkoX @vitalyiegorov I am seeing the same issue as you, I use circleci. I have tried various ways to reduce java heap size and such and it doesn't seem to be related to that. The only difference I can see for me is that locally I run on mac OS and in circleci I use the an android-node docker image. I assume that means that locally it uses 'node_modules/hermesvm/osx-bin/hermes' whereas on circleci uses 'node_modules/hermesvm/linux64-bin/hermes' so I'm guesssing the issue is related to that. Was wondering whether you guys are also building on mac locally? |
@LydGol90 absolutely, using mac locally, trying to setup appcenter.ms right now - seems to have successful build there. |
@LydGol90 |
This should be fixed in facebook/hermes#45 and will be included in 0.61 |
If you're building your android app using RN 0.60. x on CircleCI and Linux, you can set |
@mjmasn ,thanks for your contribution, but I have a question, should I move |
@ammarRajabA there's a line something like:
in You should update that to point to the new file. Moving the react.gradle back to node_modules would only work temporarily, as it would be overwritten when node_modules are installed. I haven't tried the latest RN releases with Hermes so I have no idea if these workarounds are still necessary. Would be surprised if it hadn't been fixed by now... 🤔 |
after
to
after
Now I can upload bundle build to Google Play and it doesn't crash after splash screen. |
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. |
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. |
When running with
--variant release
or doing a production build, the Hermes emit binary step fails, leaving a 0 byte bundle file. It looks like something to do with overwriting the same file, as if I cancel the build before the hermes step, then manually run the command from the Program arguments below but with a different output path, it works fine and the bytecode bundle is saved correctly.React Native version:
Steps To Reproduce
Describe what you expected to happen:
The build to succeed.
Snack, code example, or link to a repository:
Any new RN 0.60.3 app, but I made an example at https://github.com/mjmasn/HermesApp
yarn start
react-native run-android --variant release
The text was updated successfully, but these errors were encountered: