[Android] expected buildFiles file 'CMakeLists.tx' to exist

[bulkinav]

When I try build the project with 'newArchEnabled=true', I get the following error:

[CXX1409] /android/app/.cxx/Debug/v20284m3/armeabi-v7a/android_gradle_build.json : expected buildFiles file '/node_modules/@react-native-community/blur/android/build/generated/source/codegen/jni/CMakeLists.txt' to exist

Clean / rebuild doesn't solve the problem.

react-native: 0.71.4 react-native-community/blur: 4.3.0

gradle: 7.5.1 gradle plugin: 7.4.2

[bilal-korir]

I have the same bug, did you find any workaround, thanks. @bulkinav

[Abhishek2250]

I'm also getting the same issue. Any update on this?

[snamstorm]

I am also having this issue when setting newArchEnabled=true for Android.

using "react-native": "^0.71.6"

[jwarshaw]

I am also seeing this error message for react-native 0.71.6

[remi-vg]

I have the same error using react-native 0.71.8 and newArch for Android

[Ashalbulk]

just remove android/app/.cxx folder and try to rebuild

[ravindraguptacapgemini]

just remove android/app/.cxx folder and try to rebuild

Does not work with ./gradlew assembleRelease

[ravindraguptacapgemini]

just remove android/app/.cxx folder and try to rebuild

Does not work with ./gradlew assembleRelease

[kimjisena]

just remove android/app/.cxx folder and try to rebuild

I think this worked for me. Can you explain why .cxx could be the problem here?

[anazcodesap]

There are 2 solutions i found 1)set newArchEnabled=false in gradle.properties(initially it ill be true) 2)remove android/app/.cxx folder

but i dont know which would be better! if anyone knows please let me know

[sendyputra]

Workaround: I've had manually run ./gradlew generateCodegenArtifactsFromSchema in the android folder and now it seems to be working...

Originally posted by @saczx in https://github.com/react-native-async-storage/async-storage/issues/1070#issuecomment-1999653053

[andrii-drobiazko]

Solution from @sendyputra actually works, it generates all the required C++ artifacts and error goes away. There should be a bug in react-native which prevents this task from running somehow