Android build fails with new architecture on RN 0.81

[bmatasar]

Steps

1. Create new CLI project (RN 0.81, newArchitecture=true)

$ npx @react-native-community/cli@latest init AwesomeProject

2. Add react-native-config as mentioned in the installation steps

$ yarn add react-native-config
$ npx react-native-integrate react-native-config

3. Try to build on Android

$ yarn android

Result

The build fails with the output

> Task :app:configureCMakeDebug[arm64-v8a] FAILED
C/C++: CMake Error at /Users/bmatasar/git/AwesomeProject/android/app/build/generated/autolinking/src/main/jni/Android-autolinking.cmake:9 (add_subdirectory):
C/C++:   add_subdirectory given source
C/C++:   "/Users/bmatasar/git/AwesomeProject/node_modules/react-native-config/android/build/generated/source/codegen/jni/"
C/C++:   which is not an existing directory.
C/C++: Call Stack (most recent call first):
C/C++:   /Users/bmatasar/git/AwesomeProject/node_modules/react-native/ReactAndroid/cmake-utils/ReactNative-application.cmake:94 (include)
C/C++:   CMakeLists.txt:31 (include)
C/C++: CMake Error at /Users/bmatasar/git/AwesomeProject/node_modules/react-native/ReactAndroid/cmake-utils/ReactNative-application.cmake:97 (target_link_libraries):
C/C++:   Cannot specify link libraries for target "react_codegen_RNCConfigModule"
C/C++:   which is not built by this project.
C/C++: Call Stack (most recent call first):
C/C++:   CMakeLists.txt:31 (include)

[cl3i550n]

Workaround: Disable autolinking for react-native-config and link manually

My Environment:

RN: 0.81.0
RN-Config: 1.5.7
NDK: 27.1.12297006
Gradle: 8.14.3
MacOS: Sequoia 15.6.1 M2
CMake (Android SDK): 3.22.1

If you want to avoid editing node_modules, you can disable autolinking for react-native-config and add it manually in your Gradle setup.

1. Add or edit react-native.config.js at the root of your project:

module.exports = {
  dependencies: {
    'react-native-config': { platforms: { android: null } },
  },
};

2. Add or edit android/settings.gradle:

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

3. Add or edit android/app/build.gradle:

apply ....
apply ....

apply from: project(':react-native-config').projectDir.getPath() + "/dotenv.gradle" // <---- add this in top

react {
...
}

dependencies {
    implementation ...
    implementation ....

    implementation project(':react-native-config') // <---- add this

...
}

4. Add or edit src/main/java/MainApplication.kt:

import com.lugg.RNCConfig.RNCConfigPackage // <--- Add this import

// Replace getPackages to use `RNCConfigPackage`

override val reactNativeHost: ReactNativeHost =
    object : DefaultReactNativeHost(this) {

      override fun getPackages(): List<ReactPackage> {
        val packages = PackageList(this).packages.toMutableList()
        packages.add(RNCConfigPackage()) // <----- RN Config
        packages.add(VectorIconsPackage()) //  <----- RN Vector Icons
        return packages
      }

      override fun getJSMainModuleName(): String = "index"
      override fun getUseDeveloperSupport(): Boolean = BuildConfig.DEBUG
      override val isNewArchEnabled: Boolean = BuildConfig.IS_NEW_ARCHITECTURE_ENABLED
      override val isHermesEnabled: Boolean = BuildConfig.IS_HERMES_ENABLED
    }

This way, React Native won’t try to run codegen/autolinking for react-native-config (which causes the CMake error), and the module will still be available in your Android build.

[bill9222729]

diff --git a/package.json b/package.json
index 723cad901c33f4f2ff2f8e41743aa0f9d591fbe4..0372e946d91741a660b74098595b2171972dcf2a 100644
--- a/package.json
+++ b/package.json
@@ -42,7 +42,7 @@
     "@types/jest": "^29.5.12"
   },
   "dependencies": {
-  "@babel/core": "^7.25.2",
+    "@babel/core": "^7.25.2",
     "@babel/preset-env": "^7.25.0",
     "@babel/preset-react": "^7.24.7",
     "babel-jest": "^29.7.0"
@@ -54,19 +54,5 @@
     "react-native-windows": {
       "optional": true
     }
-  },
-  "codegenConfig": {
-    "name": "RNCConfigModule",
-    "type": "modules",
-    "jsSrcsDir": "./src",
-    "android": {
-      "javaPackageName": "com.luggit.reactnativeconfig"
-    },
-    "ios": {
-      "prefix": "RNC"
-    },
-    "windows": {
-      "cppNamespace": "RNCConfig"
-    }
   }
 }
\ No newline at end of file

[KeyG94]

diff --git a/package.json b/package.json
index 723cad901c33f4f2ff2f8e41743aa0f9d591fbe4..0372e946d91741a660b74098595b2171972dcf2a 100644
--- a/package.json
+++ b/package.json
@@ -42,7 +42,7 @@
"@types/jest": "^29.5.12"
},
"dependencies": {

• "@babel/core": "^7.25.2",

• "@babel/core": "^7.25.2",
  "@babel/preset-env": "^7.25.0",
  "@babel/preset-react": "^7.24.7",
  "babel-jest": "^29.7.0"
  @@ -54,19 +54,5 @@
  "react-native-windows": {
  "optional": true
  }

• },
• "codegenConfig": {
• "name": "RNCConfigModule",
• "type": "modules",
• "jsSrcsDir": "./src",
• "android": {

•  "javaPackageName": "com.luggit.reactnativeconfig"
  

• },
• "ios": {

•  "prefix": "RNC"
  

• },
• "windows": {

•  "cppNamespace": "RNCConfig"
  

• }
  }
  }
  \ No newline at end of file

Thank you, This worked for me RN 0.81.0🫡

[aditiaprasetio]

Workaround: Disable autolinking for react-native-config and link manually

My Environment:

RN: 0.81.0 RN-Config: 1.5.7 NDK: 27.1.12297006 Gradle: 8.14.3 MacOS: Sequoia 15.6.1 M2 CMake (Android SDK): 3.22.1

If you want to avoid editing node_modules, you can disable autolinking for react-native-config and add it manually in your Gradle setup.

1. Add or edit react-native.config.js at the root of your project:

module.exports = {
dependencies: {
'react-native-config': { platforms: { android: null } },
},
};
2. Add or edit android/settings.gradle:

include ':react-native-config'
project(':react-native-config').projectDir = new File(rootProject.projectDir, '../node_modules/react-native-config/android')
3. Add or edit android/app/build.gradle:

apply ....
apply ....

apply from: project(':react-native-config').projectDir.getPath() + "/dotenv.gradle" // <---- add this in top

react {
...
}

dependencies {
implementation ...
implementation ....

implementation project(':react-native-config') // <---- add this

...
}
4. Add or edit src/main/java/MainApplication.kt:

import com.lugg.RNCConfig.RNCConfigPackage // <--- Add this import

// Replace getPackages to use RNCConfigPackage

override val reactNativeHost: ReactNativeHost =
object : DefaultReactNativeHost(this) {

  override fun getPackages(): List<ReactPackage> {
    val packages = PackageList(this).packages.toMutableList()
    packages.add(RNCConfigPackage()) // <----- RN Config
    packages.add(VectorIconsPackage()) //  <----- RN Vector Icons
    return packages
  }

  override fun getJSMainModuleName(): String = "index"
  override fun getUseDeveloperSupport(): Boolean = BuildConfig.DEBUG
  override val isNewArchEnabled: Boolean = BuildConfig.IS_NEW_ARCHITECTURE_ENABLED
  override val isHermesEnabled: Boolean = BuildConfig.IS_HERMES_ENABLED
}

This way, React Native won’t try to run codegen/autolinking for react-native-config (which causes the CMake error), and the module will still be available in your Android build.

I tried this, but the app crashes when I run it.

[cl3i550n]

I tried this, but the app crashes when I run it.

Check step by step and try again.
Check environments too.

[fxricky]

+1 facing the same issue

[NiharR027]

following

[DanieleSimic]

@cl3i550n i followed your workaround and the only difference in the setup i made is in my android/app/src/main/MainApplication.kt

 override fun getPackages(): List<ReactPackage> =
            PackageList(this).packages.apply {
              // Packages that cannot be autolinked yet can be added manually here, for example:
              // add(MyReactNativePackage())
              add(RNCConfigPackage())
            }

i'm running React Native 0.81.4 and RNConfig 1.5.7

this worked for me.

i'll use this workaround until it supports the autolink

[nakshatrasinghh]

Hi everyone,

I’m currently working on configuring product flavors for my Android project and could use some community insight. I’m aiming to set up multiple flavors (e.g., dev, staging, prod — or white-label variants) with different:

• Application IDs
• API endpoints
• App names/icons
• Build configurations & dependencies

I’ve read the official docs and have a basic setup, but I’m running into issues around this CMake thing! This helped but my build.gradle does not look good!

Could anyone who’s successfully implemented complex product flavors share:

1. Their build.gradle (app-level) structure?
2. Tips for organizing flavor-specific resources and code?
3. Common pitfalls to avoid?

Any sample repos, snippets, or advice would be hugely appreciated 🙏

Thanks in advance for your help!