Unable to get the hash of the binary's bundled resources - "codepush.gradle" may have not been added to the build definition.

[SeveHo]

Hi my RN Application is crashing for release builds with the error: [CodePush] Unable to get the hash of the binary's bundled resources - "codepush.gradle" may have not been added to the build definition. Below you can find my description. Please help!!

Steps to Reproduce

1. Follow instructions for RN > 60 https://docs.microsoft.com/en-us/appcenter/distribution/codepush/rn-get-started#android-setup
2. Follow instructions for https://docs.microsoft.com/en-us/appcenter/distribution/codepush/rn-deployment#android
3. Run gradlew bundleRelease
4. Upload .aab file to the internal test track on Google Play Store
5. Upload bundle to CodePush: appcenter codepush release-react -b app.bundle -a <REDACTED>/<REDACTED> -d Staging

Resulting Setup

settings.gradle

include ':app', ':react-native-code-push'
project(':react-native-code-push').projectDir = new File(rootProject.projectDir, '../node_modules/react-native-code-push/android/app')

app/build.gradle

...
project.ext.react = [
    // custom for dep react-native-jitsi-meet
    bundleAssetName: "app.bundle",
    enableHermes: true,
]

apply from: "../../node_modules/react-native/react.gradle"
// Custom for CodePush
apply from: "../../node_modules/react-native-code-push/android/codepush.gradle"
// Added by sentry cli
apply from: "../../node_modules/@sentry/react-native/sentry.gradle"
...
android {
    buildTypes {
        debug {
        ...
        }
        release {
            signingConfig signingConfigs.release
            minifyEnabled enableProguardInReleaseBuilds
            proguardFiles getDefaultProguardFile("proguard-android.txt"), "proguard-rules.pro"

            // Important Detox-specific additions to pro-guard
            proguardFile "${rootProject.projectDir}/../node_modules/detox/android/detox/proguard-rules-app.pro"

            // Custom for CodePush
            resValue "string", "CodePushDeploymentKey", '"<Redacted>"'
        }

        // The naming convention for releaseStaging is significant due to this line https://github.com/facebook/react-native/blob/e083f9a139b3f8c5552528f8f8018529ef3193b9/react.gradle#L79
        releaseStaging {
            signingConfig signingConfigs.release
            minifyEnabled enableProguardInReleaseBuilds
            proguardFiles getDefaultProguardFile("proguard-android.txt"), "proguard-rules.pro"

            // Important Detox-specific additions to pro-guard
            proguardFile "${rootProject.projectDir}/../node_modules/detox/android/detox/proguard-rules-app.pro"

            // Custom for CodePush
            resValue "string", "CodePushDeploymentKey", '"<Redacted>"'
            // Note: It is a good idea to provide matchingFallbacks for the new buildType you create to prevent build issues
            // Add the following line if not already there
            matchingFallbacks = ['release']
        }
    }
}

MainApplication.java

...

// custom for deb react-native-jitsi-meet
import androidx.annotation.Nullable;

// custom for CodePush
import com.microsoft.codepush.react.CodePush;

public class MainApplication extends Application implements ReactApplication {

  private final ReactNativeHost mReactNativeHost =
      new ReactNativeHost(this) {
        @Override
        public boolean getUseDeveloperSupport() {
          return BuildConfig.DEBUG;
        }

        @Override
        protected List<ReactPackage> getPackages() {
          @SuppressWarnings("UnnecessaryLocalVariable")
          List<ReactPackage> packages = new PackageList(this).getPackages();
          return packages;
        }

        // Custom for CodePush
        // Override the getJSBundleFile method in order to let
        // the CodePush runtime determine where to get the JS
        // bundle location from on each app start. Specify bundle name due to change for rn-jitsi-meet
        @Override
        protected String getJSBundleFile() {
           return CodePush.getJSBundleFile("app.bundle");
        }

        @Override
        protected String getJSMainModuleName() {
          return "index";
        }

        // custom for deb react-native-jitsi-meet
        @Override
        protected @Nullable String getBundleAssetName() {
          return "app.bundle";
        }
      };

...
  @Override
  public void onCreate() {
    super.onCreate();
    SoLoader.init(this, /* native exopackage */ false);
    initializeFlipper(this, getReactNativeHost().getReactInstanceManager());
  }
}
...

Expected Behavior

The app should load the bundle from CodePush and start properly like when testet with npx react-native run-android --variant release

Actual Behavior

The app crashes with the following error

[CodePush] Loading JS bundle from "assets://app.bundle"
[CodePush] Unable to get the hash of the binary's bundled resources - "codepush.gradle" may have not been added to the build definition.
AndroidRuntime: FATAL EXCEPTION: mqt_js

Environment

• react-native-code-push version: 6.4.0
• react-native version: 63.3
• iOS/Android/Windows version: Android 10
• Does this reproduce on a debug build or release build? Release build bundle with bundleRelease command
• Does this reproduce on a simulator, or only on a physical device? Only on a physical device

[fabricio0915]

i have the same problem, when i use bundleRelease to generate an Android App Bundle i do have this issue, can anyone help us?

[fabricio0915]

In my tests the file CodePushHash was generated but, has not been copied to assets folder in the bundle

[jessamp]

I wonder if this could be related to this problem here: #1977. I was having problems when setting bundleInRelease: false. One workaround I found was manually creating these directories: android/app/build/generated/res/react/release android/app/build/generated/assets/react/release. During the build, the CodePushHash was then placed in the assets directory.

[fabricio0915]

@jessamp where you put the script to make this folders?

[fabricio0915]

in my case i use product Flavors this folder structure maybe it`s not supported by code push

[jessamp]

I set it up in my build pipelines. It's in a yaml file. If you don't use pipelines, you could probably add a post-script in the npm install step.

I also use product flavors. So in that case it would be: android/app/build/generated/res/react/<flavor name>/release

[fabricio0915]

Even creating the folder using the flavor the CodePushHash its not copied to my assets folder, i really got no ideia to fix it

[fabricio0915]

@alexandergoncharov could you help me with this issue?

[DemonWu]

我试了下改codepush.gradle文件后可以一直强制复制CodePushHash后解决了这个问题
react-native-code-push/android/codepush.gradle文件的64行除添加

                config."bundleIn${variant.buildType.name.capitalize()}" ?:
                targetName.toLowerCase().contains("release")
// 以下位置添加进去
>>>         doLast {
                    copy {
                        into("${buildDir}/intermediates")
                        into ("assets/${targetPath}") {
                            from(jsBundleDir)
                        }

                        // Workaround for Android Gradle Plugin 3.2+ new asset directory
                        into ("merged_assets/${variant.name}/merge${targetName}Assets/out") {
                            from(jsBundleDir)
                        }

                        // Workaround for Android Gradle Plugin 3.4+ new asset directory
                        into ("merged_assets/${variant.name}/out") {
                            from(jsBundleDir)
                        }
                    }
                }

可有试一下

[hungtrn75]

pull request
I followed this and it worked

[rafalzawadzki]

What I found trying to solve this:

1. I see this problem happening on Android Gradle 4.1.0+ and Gradle wrapper 6.5+. Downgrading to versions 4.0.1 and 6.2 respectively solves it.
2. Tested CodePush versions 6.3.0 through to 7.0.0, all the same
3. Clean builds always result in the issue (after ./gradlew clean), but consecutive builds are fine. This is particularly problematic in CI environments.
4. The solution given by @hungtrn75 does not work (neither changing codepush.gradle or the org.gradle.configureondemand flag)
5. Suggested change from @DemonWu did not change anything for me

Any ideas? :)

[snkhan120]

pull request
I followed this and it worked

Is it working???Anyone