Missing JS bundles when using android flavors in release builds #32338

Activity

1. MichaelBorde

   added

   Needs: Triage 🔍

   on Oct 5, 2021
2. react-native-bot

   added

   Platform: AndroidAndroid applications.Android applications.

   Tech: Bundler 📦This issue is related to the bundler (Metro, Haul, etc) used.This issue is related to the bundler (Metro, Haul, etc) used.

   Platform: LinuxBuilding on Linux.Building on Linux.

   on Oct 5, 2021
3. cortinico

   added

   Tool: Gradle

   and removed

   Tech: Bundler 📦This issue is related to the bundler (Metro, Haul, etc) used.This issue is related to the bundler (Metro, Haul, etc) used.

   on Oct 14, 2021
4. cortinico commented on Nov 1, 2021

   

   cortinico

   on Nov 1, 2021

   Contributor

   More actions

   Steps To Reproduce

   Thanks for the reproducer. I was able to reproduce it locally, yet I wasn't able to find the root cause of the problems.

   I believe this issue is happening only when you're building a multi-flavor version of an app. And is happening only when you're building more than one flavor due to a race condition on Gradle tasks.

   Potentially moving to AGP 7.x and moving that logic to use the Artifact API might solve this issue.
   If anyone else has the time to jump on this, feel free to ping me 👍
5. MichaelBorde commented on Nov 2, 2021

   

   MichaelBorde

   on Nov 2, 2021

   Author

   More actions

   I believe this issue is happening only when you're building a multi-flavor version of an app. And is happening only when you're building more than one flavor due to a race condition on Gradle tasks.

   I think these two assumptions are correct from my experience.
6. joeyfigaro commented on Nov 7, 2021

   

   joeyfigaro

   on Nov 7, 2021

   More actions

   Also affected by this issue. Am using dev, beta, and prod flavors in a current application, and all *Debug builds (or anything with bundling disabled) fails. Metro is running as expected during my testing/attempts.
7. hotaryuzaki commented on Dec 10, 2021

   

   hotaryuzaki

   on Dec 10, 2021

   More actions

   maybe you can try this solution here
8. lfmatosm commented on May 25, 2022

   

   lfmatosm

   on May 25, 2022

   More actions

   Still happens on react-native==0.67.4, with com.android.tools.build:gradle==4.2.2 and gradle==7.2. Proguard is disabled on my app. Hermes is currently enabled, but the same problem happens if you disable it. Also, the problem was simuated on Linux environment. On macOs, this didn't happen.

   In my case, the error happens when building a single flavor from an app with multiple flavors configured. We have multiple types on our build stage (dev, hml, etc.). Our android/app/build.gradle looks like this:

   /*some stuff*/
   
   android {
       /*more stuff*/
   
       buildTypes {
           release {
               /*release definition*/
           }
   
           dev {
               /*dev definition*/
           }
   
           hml {
               /*hml definition*/
           }
       }
   
       flavorDimensions 'version'
   
       productFlavors {
           firstFlavor {
               /*flavor definition*/
           }
   
           secondFlavor {
               /*flavor definition*/
           }
   
          /*other flavors*/
       }
   }

   So, for any flavor, there's actually 3 different APKs. So our assemble command looks like this:

   ./gradlew assembleFirstFlavorDev assembleFirstFlavorHml assembleFirstFlavorRelease

   The above command generates 3 APKs, where some of them randomly doesn't includes the index.android.bundle. I didn't track down which tasks were being executed outside the required order, but that's probably the reason for the problem, as mentioned by @cortinico.

   If you build one type at a time, everything works smoothly:

   ./gradlew assembleFirstFlavorDev
   ./gradlew assembleFirstFlavorHml
   ./gradlew assembleFirstFlavorRelease

   Is worth to notice that this problem started happening only after upgrading from react-native version 0.63.2 to 0.67.4. On the previous version, the Android Gradle plugin was 3.5.3 and gradle was 6.2.

   👍React with 👍1Reacted by Ivan Harelik
9. 9christian9 commented on Feb 9, 2023

   

   9christian9

   on Feb 9, 2023

   Last edited by 9christian9

   More actions

   Ciao,
   I'm writing for all the people who, like me, have experienced this problem.

   Affected Versions

   • React Native: 0.67.x
   • Gradle 7.2.x - 7.3.x

   The common error

   Unable to load script. Make sure you're either running a Metro server (run 'react-native start') or that your bundle 'index.android.bundle' is packaged correctly for release.

   In short, index.android.bundle is missing.
   Common problem when trying to use productFlavors.

   The problem
   I found that the problem is in a native react gradle task, to be precise in the copy task called currentAssetsCopyTask located in react.gradlefile.
   As I understand, this "task" is responsible for copying the assets and in particular index.android.bundle and pasting them into the temporary directories used to generate the APK.

   The solution
   I created a repo that with a js script solves the problem before building the android app
   https://github.com/9christian9/FIX-Android-productFlavors-RN0.67-gradle7.2-7.3

   I hope this will help.
   With ♥ by Christian
10. lucasantarella commented on Feb 14, 2023

    

    lucasantarella

    on Feb 14, 2023

    More actions

    For those still looking, looks like this report is similar to the issue #31157
11. cortinico commented on Dec 4, 2023

    

    cortinico

    on Dec 4, 2023

    Contributor

    More actions

    Closing as flavors support has been completely rewritten in React Native 0.71
    Please migrate to that version and try again. If the issue persists open a new bug report
12. cortinico

    closed this as completedon Dec 4, 2023