Scribd
Upload
35 views1 page

Solution

The issue discussed was resolved by running a specific command to bundle the React Native application for Android before each build. The command used was 'npx react-native bundle' followed by 'cd android && ./gradlew assembleRelease', which successfully built the project without the need for the --assets-dest option. Experimentation with the hermes-engine version did not impact the issue, indicating it was unrelated to Hermes.

Uploaded by

Raman deep
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
35 views1 page

Solution

The issue discussed was resolved by running a specific command to bundle the React Native application for Android before each build. The command used was 'npx react-native bundle' followed by 'cd android && ./gradlew assembleRelease', which successfully built the project without the need for the --assets-dest option. Experimentation with the hermes-engine version did not impact the issue, indicating it was unrelated to Hermes.

Uploaded by

Raman deep
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
You are on page 1/ 1

[Link]

com/react-native-community/upgrade-support/issues/38

[Link]
build-gradle-L81

[Link]

Update

I solved this issue by doing this before each build:

npx react-native bundle --platform android --dev false --entry-file [Link] --


bundle-output android/app/src/main/assets/[Link]
and then run

cd android
./gradlew assembleRelease
Adding the --assets-dest option to the command then gave a duplicate assets error
when building, so I skipped that and it works perfectly.

Also, I tried experimenting with the version of hermes-engine, but that had no
effect. This issue doesn't seem to be anything to do with Hermes.

You might also like