My problem was the same as yours, but the command (.\gradlew app:assembleRelease -x bundleReleaseJsAndAssets) solved it for me now I am facing another issue, which is that when I run the command (npx react-native run-android) everything is fine, but when I build an APK by using this command (.\gradlew app:assembleRelease -x bundleReleaseJsAndAssets) it’s crashes.

Hello! @therafibhuiyan
It must crash.
Because .\gradlew app:assembleRelease -x bundleReleaseJsAndAssets, that -x I believe means without.
So, there will be no bundling for Release of JS and Assists.
So, it must crash.
I will never ever use this -x bundleReleaseJsAndAssets again. 😃

@OmarThinks The development of my application has been completed but I am unable to push it to the production build due to this issue.

My problem was the same as yours, but the command .\gradlew app:assembleRelease -x bundleReleaseJsAndAssets solved it for me now I am facing another issue, which is that when I run the command npx react-native run-android everything is fine, but when I build an APK by using this command .\gradlew app:assembleRelease -x bundleReleaseJsAndAssets it’s crashes.

In general, using any ./gradlew <command> is a bad practice. You should be using react-native run-android.

The -x flag will obviously make your app crash as you’re not bundling JS and images inside the final app.

RN official documentation According to the RN official documentation if we want to create an abb file then we have to use ./gradlew bundleRelease. If this is a bad practice then why in the official documentation they mentioned this command to generate an abb file?

@OmarThinks After doing some research, I was able to build a working APK. First I have to install React-Native globally by using npm install -g react-native-cli. I changed the ExecutionPolicy by running Set-ExecutionPolicy Unrestricted in PowerShell on administrator power, Then, I created a folder called assets in android/app/src/main/ this directory. Once that’s done, I run react-native bundle --platform android --dev false --entry-file index.js --bundle-output android/app/src/main/assets/index.android.bundle --assets-dest android/app/src/main/res from the root of the project and then run this ./gradlew assembleRelease -x bundleReleaseJsAndAssets from the android folder. Now I just have to create an abb file and let’s see what happens.

Just a small heads up that I’ve tested this on 0.71 today and I can confirm that everything works as expected

Hello @OmarThinks , did you tried on Mac or Linux?

I have the same issue in both Windows 11 machines and i’m gonna try it on Mac from zero.

> Task :app:createBundleReleaseJsAndAssets FAILED
Execution failed for task ':app:createBundleReleaseJsAndAssets'.
> Process 'command 'cmd'' finished with non-zero exit value 1

@therafibhuiyan .\gradlew app:assembleRelease
.\gradlew bundleRelease
Are correct.
Or also you can use android studio to generate the APK or Bundle.
Top Bar => Build => Generate Signed Bundle / APK
All of these should work.
But, I meant that this -x bundleReleaseJsAndAssets is the one that I will never use again. 😃 😃

Yeah. I agree with you! The React Native Team is doing Great work. I really can’t thank them enough.
They saved our souls from having to write Java.
I can’t acknowledge their hard work enough. But, I just would really appreciate resolving that tiny little bug. 😃 😃

My problem was the same as yours, but the command .\gradlew app:assembleRelease -x bundleReleaseJsAndAssets solved it for me now I am facing another issue, which is that when I run the command npx react-native run-android everything is fine, but when I build an APK by using this command .\gradlew app:assembleRelease -x bundleReleaseJsAndAssets it’s crashes.

Hey @OmarThinks @cortinico ,

It actually worked on Mac with M1 chip. Just following the MacOS Android guides from React Native site.

My app is using react-native@0.71.1 compiled with Zulu11.

We also tried on Windows 11 and it failed. So it seems it’s a Windows issue.

Hope it helps 😃

My problem was the same as yours, but the command .\gradlew app:assembleRelease -x bundleReleaseJsAndAssets solved it for me now I am facing another issue, which is that when I run the command npx react-native run-android everything is fine, but when I build an APK by using this command .\gradlew app:assembleRelease -x bundleReleaseJsAndAssets it’s crashes.

In general, using any ./gradlew <command> which are not described in the official documentation, is a bad practice, as you’re using flags that might impact your build.

The -x flag will obviously make your app crash as you’re not bundling JS and images inside the final app.

EDIT: Clarification

@7geekerLarr This is because you have a space in your path (C:\PROYECTOS 2023\xaf). A fix for this has been added - see this comment - and will be available in the next version or point release for RN71.

• Gradle detected a problem with the following location: ‘D:\Dev\New folder\DeleteLater\AwesomeProject\android\app\build\generated\res\react\release’. Reason: Task ‘:app:mergeReleaseResources’ uses this output of task ‘:app:createBundleReleaseJsAndAssets’ without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed. Please refer to https://docs.gradle.org/7.5.1/userguide/validation_problems.html#implicit_dependency for more details about this problem.

@OmarThinks could you try again making sure there are no spaces in your path, as this could be a duplicate of https://github.com/facebook/react-native/issues/34878 ?

I tried as you told me, sir! That was the result.

Thanks for the heads up. This seems to be a Windows specific issue. We’ll have to look into it next week.

Thanks for the update. That’s expected as we’re still in RC. You would need a beta of Android Studio to open it.

Does it work from the command line though?

There are two links to this error. Stackoverflow Github

@therafibhuiyan the two links you shared are for way older version of RN and makes impossible for us to reproduce/fix those kind of issues.

I am testing it right now.

@OmarThinks please let me know if in 0.71 the issue is fixed

There are two links to this error. Stackoverflow Github

@cortinico As @therafibhuiyan mentioned, I and @therafibhuiyan are not the only people suffering from this tiny little bug.
I guess too many are.

Thank you so much! 😃 😃

There are two links to this error. Stackoverflow Github

It might be a problem with my setup, but if we search on the internet for the exact same issue, we’ll find out that there are many people experiencing this issue as well

Could you share those links please?

Let’s just forget about it all and just focus on what @OmarThinks says. He just generated the template and did not add any other code to the template, just signed the keys but still got the same problem. What are you’ll gonna say about this?

If that is the case, then this is a bug I’d like to address/handle. @OmarThinks can you share your full build log? Also can you try the same on the latest RC of 0.71.x as I believe this issue is already solved:

npx react-native init AwesomeProject --version next

@cortinico It might be a problem with my setup, but if we search on the internet for the exact same issue, we’ll find out that there are many people experiencing this issue as well. Various approaches are being taken to fix this. Let’s just forget about it all and just focus on what @OmarThinks says. He just generated the template and did not add any other code to the template, just signed the keys but still got the same problem. What are you’ll gonna say about this?

According to the RN official documentation if we want to create an abb file then we have to use ./gradlew bundleRelease. If this is a bad practice then why in the official documentation they mentioned this command to generate an abb file?

Sorry for being confusing, I’ve edited my answer with a clarification. In general the CLI offers a variety of commands (like react-native run-android) that help you achieve most of the things you need. For bundleRelease there is no such command (we’re actually recently introduced react-native build-android so we might consider it for this scenario).

Then, I created a folder called assets in android/app/src/main/ this directory. Once that’s done, I run react-native bundle --platform android --dev false --entry-file index.js --bundle-output android/app/src/main/assets/index.android.bundle --assets-dest android/app/src/main/res from the root of the project and then run this ./gradlew assembleRelease -x bundleReleaseJsAndAssets from the android folder

In general, you should not invoke react-native bundle manually. If you just invoke ./gradlew bundleRelease, the bundling will be done for you. The fact that the task is failing with Execution failed for task ':app:bundleReleaseJsAndAssets'. means that there is an underlying issue in your setup, taht you’re not fixing and you’re just circumventing

@7geekerLarr This is because you have a space in your path (C:\PROYECTOS 2023\xaf). A fix for this has been added - see this comment - and will be available in the next version or point release for RN71.

This solved it. Now I’m kinda scared to put spaces in folder paths on my machine…

@OmarThinks Ok thanks, i’m gonna try on Mac M1 and comment if the issue is solved. 😃

Thanks for the report. There is something going on with the Windows setup on 0.71 that needs to be investigated. I don’t have a Windows machine with me at the moment, I’ll follow up as soon as I have one (cc @kelset @mganandraj)

@cortinico
I will try it ASAP, sir!
I am just kinda busy now.
I will try it in a few hours, and provide feedback! 😃 😃

@therafibhuiyan I am not 100% sure what it means. Maybe he is right.
But the app crashes every time I do this. LOL! I tried lots of things. 😃

My problem was the same as yours, but the command (.\gradlew app:assembleRelease -x bundleReleaseJsAndAssets) solved it for me now I am facing another issue, which is that when I run the command (npx react-native run-android) everything is fine, but when I build an APK by using this command (.\gradlew app:assembleRelease -x bundleReleaseJsAndAssets) it’s crashes.

Hello! @therafibhuiyan It must crash. Because .\gradlew app:assembleRelease -x bundleReleaseJsAndAssets, that -x I believe means without. So, there will be no bundling for Release of JS and Assists. So, it must crash. I will never ever use this -x bundleReleaseJsAndAssets again. 😃

Hello! @OmarThinks Someone told me it basically binds all of my app’s artifacts and makes a release version APK ready to be deployed for production. But it seems to me that I have made a mistake by using this command.