Flavors & App Bundle missing index.android.bundle with proguard enabled #31157

lorenzoangelini · 2021-03-14T22:20:33Z

Issue

We use the flavors into our apps to use different version. We have dev, test and prod. When we have upgraded to 0.63 (same with 0.64), to classpath("com.android.tools.build:gradle:3.5.3") and distributionUrl=https://services.gradle.org/distributions/gradle-6.2-all.zip and proguard enabled, we cannot use the appbundle.
when we run ./gradlew bundleDevRelease -> we cannot find into the app-dev-release.aab the index.android.bundle. This cause a crash when open the app.
If we run this command : ./gradlew bundleRelease -> it build all variants
app-dev-release.aab -> missing
app-test-release.aab -> index.android.bundle present
app-prod-release.aab -> index.android.bundle present

Description

Please provide a clear and concise description of what the bug is. Include screenshots if needed.
Please test using the latest React Native release to make sure your issue has not already been fixed: https://reactnative.dev/docs/upgrading.html

React Native version:

System:
OS: macOS 10.15.7
CPU: (4) x64 Intel(R) Core(TM) i5-7360U CPU @ 2.30GHz
Memory: 944.16 MB / 16.00 GB
Shell: 5.7.1 - /bin/zsh
Binaries:
Node: 14.15.4 - /usr/local/bin/node
Yarn: 1.13.0 - /usr/local/bin/yarn
npm: 6.14.10 - /usr/local/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
Managers:
CocoaPods: 1.10.1 - /usr/local/bin/pod
SDKs:
iOS SDK:
Platforms: iOS 14.0, DriverKit 19.0, macOS 10.15, tvOS 14.0, watchOS 7.0
Android SDK:
API Levels: 23, 27, 28, 29
Build Tools: 26.0.2, 27.0.3, 28.0.3, 29.0.2, 29.0.3
System Images: android-19 | Google APIs Intel x86 Atom, android-23 | Google APIs Intel x86 Atom_64, android-27 | Intel x86 Atom_64, android-28 | Google APIs Intel x86 Atom
Android NDK: Not Found
IDEs:
Android Studio: 4.1 AI-201.8743.12.41.6953283
Xcode: 12.0/12A7209 - /usr/bin/xcodebuild
Languages:
Java: 1.8.0_201 - /usr/bin/javac
npmPackages:
@react-native-community/cli: Not Found
react: 17.0.1 => 17.0.1
react-native: 0.64.0 => 0.64.0
react-native-macos: Not Found
npmGlobalPackages:
react-native: Not Found

Steps To Reproduce

1.Create a new project: npx react-native init AppName --template react-native-template-typescript
2. Add to gradle.build :
productFlavors {
prod {
}
dev {
applicationId 'com.appname.dev'
resValue "string", "build_config_package", "com.appname"
}
test {
applicationId 'com.appname.test'
resValue "string", "build_config_package", "com.appname"
}
}
3. Enable Proguard
4. run into android folder : ./gradlew clean && ./gradlew bundleDevRelease

Expected Results

Obtain an .aab file into android/build/outputs/bundle/devRelease. when i open the .aab i expect to find the folder base and into the base the folder assets that contain the index.android.bundle.

gedeagas · 2021-03-24T05:49:07Z

@lorenzoangelini This issue has now been resolved in 0.64.
#30177

lorenzoangelini · 2021-03-24T09:24:22Z

@gedeagas i reproduce this issue when proguard is active

gedeagas · 2021-03-24T15:14:44Z

@lorenzoangelini Interesting, do you mind providing a git repo of the problem?

@renopp This is probably related to your case ( multiflavors, prod aab dosen't have index.android.bundle, etc ). Let's try to fix this if there is a problem here.

lorenzoangelini · 2021-03-25T11:56:56Z

@gedeagas with a new project i reproduce this issue when i using flavors.

davwheat · 2021-03-26T17:48:27Z

Can reproduce on RN 0.64.0. Worked fine before the upgrade on 0.63.x. 🤔

I'd share the git repo, but this app is private for a client.

I don't use productFlavors, only buildTypes.

Debug and prod APKs work fine. Haven't tested a debug AAB.

// build.gradle
buildTypes {
    release {
        signingConfig signingConfigs.release
        minifyEnabled enableProguardInReleaseBuilds
        proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'
        minifyEnabled true
        shrinkResources true
    }
    releaseUnsigned {
        initWith release
        signingConfig null
        // needed to prevent react native dependency code failing
        // to build
        matchingFallbacks =  ['release']
    }
}

// ------------------------------------------------

// proguard-rules.pro
-keep public class com.horcrux.svg.** {*;}

react-native info output

info Fetching system and libraries information...
System:
    OS: Windows 10 10.0.19042
    CPU: (6) x64 Intel(R) Core(TM) i5-9600K CPU @ 3.70GHz
    Memory: 3.70 GB / 15.94 GB
  Binaries:
    Node: 15.1.0 - ~\AppData\Local\Temp\yarn--1616780838243-0.2835069363144411\node.CMD
    Yarn: 1.22.5 - ~\AppData\Local\Temp\yarn--1616780838243-0.2835069363144411\yarn.CMD
    npm: 7.6.3 - c:\users\david\appdata\roaming\npm\npm.CMD
    Watchman: Not Found
  SDKs:
    Android SDK:
      API Levels: 23, 24, 25, 26, 28, 29, 30
      Build Tools: 28.0.3, 29.0.2, 30.0.2, 30.0.3
      System Images: android-26 | Android Wear Intel x86 Atom, android-28 | China version of Wear OS Intel x86 Atom, android-28 | Wear OS Intel x86 Atom, android-30 | Google APIs Intel x86 Atom
      Android NDK: Not Found
    Windows SDK: Not Found
  IDEs:
    Android Studio: Not Found
    Visual Studio: 15.9.28307.1321 (Visual Studio Community 2017)
  Languages:
    Java: 11.0.7 - c:\program files\adoptopenjdk\jdk-11.0.7.10-hotspot\bin\javac.EXE
  npmPackages:
    @react-native-community/cli: Not Found
    react: 17.0.1 => 17.0.1
    react-native: ^0.64.0 => 0.64.0
    react-native-windows: Not Found
  npmGlobalPackages:
    *react-native*: Not Found

gedeagas · 2021-03-26T17:53:46Z

@davwheat so it's working on RN 0.63 but not 0.64? hmm.. that is strange.
I will be looking at this on Monday. Thanks for the report.

davwheat · 2021-03-26T17:55:46Z

It was working before I upgraded on 20th March -- I suppose it could have come in from another change I've made, but I doubt any JS changes would cause it, and I haven't tinkered with my build process at all (except the upgrade process).

If you want me to test anything or give you more info, let me know :)

lorenzoangelini · 2021-03-26T17:58:47Z

@davwheat me too, i don't have any problem with 0.62, the app bundle was build correctly.

gedeagas · 2021-03-26T18:01:26Z

@davwheat do you also have proguard turned on like @lorenzoangelini ?

davwheat · 2021-03-26T18:15:33Z

@gedeagas Yes, I use proguard, including a custom rule which I posted above.

danaelisanicolas · 2021-03-31T06:21:53Z

Any updates on this? We're also having issues on bundling android releases with proguard enabled

This commit fixes Flavors & App Bundle missing index.android.bundle with proguard enabled facebook#31157 (comment)

renopp · 2021-03-31T07:23:47Z

@lorenzoangelini @davwheat @danaelisanicolas
I just created a PR to fix the issue, kindly check

mikehardy · 2021-03-31T13:41:10Z

Apologies for the tangent, but the I was scanning the react-native issues list for a different reason and saw this - I patterned a change to the react-native-elements font-copy task after the changes done here in the react-native repo to handle gradle 4.1+, and it's the same code area - if anyone using react-native-elements notices that for app bundles that use flavors and variants you aren't seeing your fonts copied, it may be that the same sort of change needs to be carried into the react-native-elements font-copy gradle task, c.f. oblador/react-native-vector-icons#1307

danaelisanicolas · 2021-03-31T22:46:36Z

Hi, Actually mine got fixed when I change from:

buildTypes {
    debug {
        signingConfig signingConfigs.debug
    }
    release {
        // Caution! In production, you need to generate your own keystore file.
        // see https://reactnative.dev/docs/signed-apk-android.
        minifyEnabled true
        shrinkResources true
        signingConfig signingConfigs.release
        proguardFiles getDefaultProguardFile("proguard-android.txt"), "proguard-rules.pro"
    }
}

to just:

buildTypes {
    debug {
        signingConfig signingConfigs.debug
    }
    release {
        // Caution! In production, you need to generate your own keystore file.
        // see https://reactnative.dev/docs/signed-apk-android.
        minifyEnabled enableProguardInReleaseBuilds
        signingConfig signingConfigs.release
        proguardFiles getDefaultProguardFile("proguard-android.txt"), "proguard-rules.pro"
    }
}

and for context my proguard file looks like this:

-keep class com.facebook.hermes.unicode.** { *; }
-keep class com.facebook.jni.** { *; }
-keep public class com.horcrux.svg.** {*;}

Please correct me if i'm wrong, but from what I understand, minifyEnabled WITHOUT the proguard reference doesn't keep the files (during minifying and shrinking) that hermes, jni, and svg needs which then gets null reference pointer exception when bundled and ran.

davwheat · 2021-03-31T23:38:15Z

I think the bigger issue is that we shouldn't suddenly have builds break for no apparent reason, especially when it's not super easy to test aabs, and when it's not listed in the changelog.

The PR is a simple one line fix (I haven't tested it personally, but I trust that it works) so merging that should be a priority over other workarounds, otherwise people will put off upgrading RN as it breaks their app.

hotaryuzaki · 2021-12-10T11:58:02Z

Hi, Actually mine got fixed when I change from:

buildTypes {
    debug {
        signingConfig signingConfigs.debug
    }
    release {
        // Caution! In production, you need to generate your own keystore file.
        // see https://reactnative.dev/docs/signed-apk-android.
        minifyEnabled true
        shrinkResources true
        signingConfig signingConfigs.release
        proguardFiles getDefaultProguardFile("proguard-android.txt"), "proguard-rules.pro"
    }
}

to just:

buildTypes {
    debug {
        signingConfig signingConfigs.debug
    }
    release {
        // Caution! In production, you need to generate your own keystore file.
        // see https://reactnative.dev/docs/signed-apk-android.
        minifyEnabled enableProguardInReleaseBuilds
        signingConfig signingConfigs.release
        proguardFiles getDefaultProguardFile("proguard-android.txt"), "proguard-rules.pro"
    }
}

and for context my proguard file looks like this:

-keep class com.facebook.hermes.unicode.** { *; }
-keep class com.facebook.jni.** { *; }
-keep public class com.horcrux.svg.** {*;}

Please correct me if i'm wrong, but from what I understand, minifyEnabled WITHOUT the proguard reference doesn't keep the files (during minifying and shrinking) that hermes, jni, and svg needs which then gets null reference pointer exception when bundled and ran.

my problem was app would crash when open (AAB), but no issue for debug app & APK.
fixed with remove shrinkResources in build.gradle.
thanks @danaelisanicolas

my error log:

12-10 15:04:34.984 27112 27112 E AndroidRuntime: FATAL EXCEPTION: main
12-10 15:04:34.984 27112 27112 E AndroidRuntime: Process: com.brambang.apps, PID: 27112
12-10 15:04:34.984 27112 27112 E AndroidRuntime: java.lang.AssertionError: APK bundle must contain the expected embedded asset index.android.bundle
12-10 15:04:34.984 27112 27112 E AndroidRuntime: 	at expo.modules.updates.l.e.a(Unknown Source:147)
12-10 15:04:34.984 27112 27112 E AndroidRuntime: 	at expo.modules.updates.l.e.g(Unknown Source:50)
12-10 15:04:34.984 27112 27112 E AndroidRuntime: 	at expo.modules.updates.l.e.e(Unknown Source:10)
12-10 15:04:34.984 27112 27112 E AndroidRuntime: 	at expo.modules.updates.l.g.x(Unknown Source:64)
12-10 15:04:34.984 27112 27112 E AndroidRuntime: 	at expo.modules.updates.l.g.B(Unknown Source:96)
12-10 15:04:34.984 27112 27112 E AndroidRuntime: 	at expo.modules.updates.f.D(Unknown Source:75)
12-10 15:04:34.984 27112 27112 E AndroidRuntime: 	at expo.modules.updates.f.s(Unknown Source:5)
12-10 15:04:34.984 27112 27112 E AndroidRuntime: 	at expo.modules.updates.UpdatesPackage$a.b(Unknown Source:12)
12-10 15:04:34.984 27112 27112 E AndroidRuntime: 	at f.a.e.createReactInstanceManager(Unknown Source:33)
12-10 15:04:34.984 27112 27112 E AndroidRuntime: 	at com.facebook.react.s.a(Unknown Source:9)
12-10 15:04:34.984 27112 27112 E AndroidRuntime: 	at com.brambang.apps.MainApplication.onCreate(Unknown Source:11)
12-10 15:04:34.984 27112 27112 E AndroidRuntime: 	at android.app.Instrumentation.callApplicationOnCreate(Instrumentation.java:1193)
12-10 15:04:34.984 27112 27112 E AndroidRuntime: 	at android.app.ActivityThread.handleBindApplication(ActivityThread.java:6991)
12-10 15:04:34.984 27112 27112 E AndroidRuntime: 	at android.app.ActivityThread.access$1500(ActivityThread.java:257)
12-10 15:04:34.984 27112 27112 E AndroidRuntime: 	at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1982)
12-10 15:04:34.984 27112 27112 E AndroidRuntime: 	at android.os.Handler.dispatchMessage(Handler.java:106)
12-10 15:04:34.984 27112 27112 E AndroidRuntime: 	at android.os.Looper.loop(Looper.java:236)
12-10 15:04:34.984 27112 27112 E AndroidRuntime: 	at android.app.ActivityThread.main(ActivityThread.java:8056)
12-10 15:04:34.984 27112 27112 E AndroidRuntime: 	at java.lang.reflect.Method.invoke(Native Method)
12-10 15:04:34.984 27112 27112 E AndroidRuntime: 	at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:656)
12-10 15:04:34.984 27112 27112 E AndroidRuntime: 	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:967)

staltz · 2022-02-04T12:17:38Z

I was also missing index.android.bundle after updating RN 0.64.x => 0.66.x and what worked for me was calling

./gradlew assembleMyFlavorRelease

instead of

./gradlew assembleRelease

I was using the latter previously, which builds all flavors at once. Apparently if you assemble each flavor one at a time, it works. Here's my codebase in case anyone wants to explore more details: staltz/manyverse@c84843a

9christian9 · 2023-02-09T22:34:39Z

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

github-actions · 2023-11-30T05:40:44Z

This issue is stale because it has been open 180 days with no activity. Remove stale label or comment or this will be closed in 7 days.

github-actions · 2023-12-07T05:40:55Z

This issue was closed because it has been stalled for 7 days with no activity.

lorenzoangelini added the Needs: Triage 🔍 label Mar 14, 2021

renopp added a commit to renopp/react-native that referenced this issue Mar 31, 2021

hotfix(react.gradle): fixing currentBundleTask

e027cee

This commit fixes Flavors & App Bundle missing index.android.bundle with proguard enabled facebook#31157 (comment)

renopp mentioned this issue Mar 31, 2021

Fixing Flavors & App Bundle missing index.android.bundle with proguard enabled #31279

Closed

Dimon70007 mentioned this issue May 30, 2021

fixed copying index.android.bundle with gradle 4.1 #31633

Closed

MichaelBorde mentioned this issue Oct 5, 2021

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

Closed

hotaryuzaki mentioned this issue Dec 10, 2021

AAB crash java.lang.AssertionError: APK bundle must contain the expected embedded asset index.android.bundle expo/expo#15499

Closed

xD3CODER mentioned this issue Jan 15, 2022

SUBMIT 'index.android.bundle' missing when submitting to Playstore expo/eas-cli#908

Closed

github-actions bot added the Stale There has been a lack of activity on this issue and it may be closed soon. label Nov 30, 2023

github-actions bot closed this as completed Dec 7, 2023

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Flavors & App Bundle missing index.android.bundle with proguard enabled #31157

Flavors & App Bundle missing index.android.bundle with proguard enabled #31157

lorenzoangelini commented Mar 14, 2021

gedeagas commented Mar 24, 2021

lorenzoangelini commented Mar 24, 2021

gedeagas commented Mar 24, 2021

lorenzoangelini commented Mar 25, 2021

davwheat commented Mar 26, 2021 •

edited

Loading

gedeagas commented Mar 26, 2021 •

edited

Loading

davwheat commented Mar 26, 2021

lorenzoangelini commented Mar 26, 2021

gedeagas commented Mar 26, 2021

davwheat commented Mar 26, 2021

danaelisanicolas commented Mar 31, 2021

renopp commented Mar 31, 2021

mikehardy commented Mar 31, 2021

danaelisanicolas commented Mar 31, 2021 •

edited

Loading

davwheat commented Mar 31, 2021

hotaryuzaki commented Dec 10, 2021

staltz commented Feb 4, 2022 •

edited

Loading

9christian9 commented Feb 9, 2023

github-actions bot commented Nov 30, 2023

github-actions bot commented Dec 7, 2023

Flavors & App Bundle missing index.android.bundle with proguard enabled #31157

Flavors & App Bundle missing index.android.bundle with proguard enabled #31157

Comments

lorenzoangelini commented Mar 14, 2021

Issue

Description

React Native version:

Steps To Reproduce

Expected Results

gedeagas commented Mar 24, 2021

lorenzoangelini commented Mar 24, 2021

gedeagas commented Mar 24, 2021

lorenzoangelini commented Mar 25, 2021

davwheat commented Mar 26, 2021 • edited Loading

gedeagas commented Mar 26, 2021 • edited Loading

davwheat commented Mar 26, 2021

lorenzoangelini commented Mar 26, 2021

gedeagas commented Mar 26, 2021

davwheat commented Mar 26, 2021

danaelisanicolas commented Mar 31, 2021

renopp commented Mar 31, 2021

mikehardy commented Mar 31, 2021

danaelisanicolas commented Mar 31, 2021 • edited Loading

davwheat commented Mar 31, 2021

hotaryuzaki commented Dec 10, 2021

staltz commented Feb 4, 2022 • edited Loading

9christian9 commented Feb 9, 2023

github-actions bot commented Nov 30, 2023

github-actions bot commented Dec 7, 2023

davwheat commented Mar 26, 2021 •

edited

Loading

gedeagas commented Mar 26, 2021 •

edited

Loading

danaelisanicolas commented Mar 31, 2021 •

edited

Loading

staltz commented Feb 4, 2022 •

edited

Loading