react-native-screens
react-native-screens copied to clipboard
Android Build Error - Execution failed for task ':react-native-screens:configureCMakeRelWithDebInfo'
Description
When assembling a dev release build on android I get a build error.
Error shown is :
- What went wrong:
Execution failed for task ':react-native-screens:configureCMakeRelWithDebInfo'.
[CXX1405] error when building with cmake using /Users/vagrant/git/node_modules/react-native-screens/android/CMakeLists.txt: Build command failed. Error while executing java process with main class com.google.prefab.cli.AppKt with arguments {--build-system cmake --platform android --abi armeabi-v7a --os-version 24 --stl c++_shared --ndk-version 24 --output /Users/vagrant/git/node_modules/react-native-screens/android/.cxx/RelWithDebInfo/513j6x30/prefab/armeabi-v7a/prefab}
Usage: prefab [OPTIONS] [PACKAGE_PATH]...
Error: Missing argument "PACKAGE_PATH".
Steps to reproduce
- Create a new project "npx [email protected] init RNScreenTest --version 0.68.7"
- run yarn install
- Run project via release variant in android studio or via command line
- See error
ERROR : > Task :react-native-screens:configureCMakeRelWithDebInfo FAILED C/C++: prefabUsage: prefab [OPTIONS] [PACKAGE_PATH]... C/C++: prefabError: Missing argument "PACKAGE_PATH".
Snack or a link to a repository
https://github.com/FraserKemp/test-react-native-screens
Screens version
3.30.1
React Native version
0.68.7
Platforms
Android
JavaScript runtime
JSC
Workflow
React Native (without Expo)
Architecture
Paper (Old Architecture)
Build type
Release mode
Device
None
Device model
No response
Acknowledgements
Yes
I downgrade version [3.29.0], it work
I also downgraded for now 👍
Hi @FraserKemp, thanks for submitting this issue! Let me investigate it 🔎
I am also having same issue - React native - 0.70.6 react-native-screens - "^3.15.0"
I am also having same issue - React native - 0.70.6 react-native-screens - "^3.15.0"
instead of "^3.15.0" set "3.29.0" (without ^)
@kumarGautamAramark This seems to be issue with React Native, rather than error from Screens. I found that there were some issues with prefab already in 0.70 - https://github.com/facebook/react-native/issues/34871
@wieckowskimateusz yeah, setting "3.29.0" did resolve the issue. Thank you.
I can confirm this exists on my side 👍 We'll try find a solution for that. Thanks!
Confirming downgrading to "3.29.0" instead of "^3.29.0" did resolve the issue.
Yep 3.29 works for me. Adding it to my lock file.
Hi @tboba I am also getting this issue here's the detail of my project.
"react-native": "0.69.12" "react-native-screens": "^3.29.0",
And I had a patch previously for version 3.29.0
and it was working fine 3 days before the last version release came out 3.30.1
.
Patch:
build issue:
Please provide a solution for this.
I am also having same issue - React native - 0.70.6 react-native-screens - "^3.15.0"
instead of "^3.15.0" set "3.29.0" (without ^)
This fixed my issue, Thanks @wieckowskimateusz for saving my day!
Hi everyone, thanks for confirming that on your scenario this error also happens! I can observe, that the case with PACKAGE_PATH
error happens only on projects with the React Native 0.68. However, the error with ReactAndroidConfig.cmake
happens only on projects with the React Native 0.69 - 0.70. I've already discussed this issue with @piaskowyk and we're taking a look on what went wrong 👀
I am also having same issue - React native - 0.70.6 react-native-screens - "^3.15.0" You have getting same issue in react-native-screen with react-native 0.70.10 then I have update react-native-screen with 3.18.0 then my issue has been resolved
Hi all! This fix has been included in the newest release of React Native Screens: 3.31.0-rc.0! 🎉 Please note that this is a release candidate for upcoming version of Screens: 3.31.0. If you encounter any issues or inconveniences, please reach out to use by submitting an issue! Thanks 💙
Release notes: https://github.com/software-mansion/react-native-screens/releases/tag/3.31.0-rc.0
cc @FraserKemp @hau1412 @kumarGautamAramark @wieckowskimateusz @ardneved @frankfuu @usamaabutt @pradeep-tomer
@tboba Awesome thanks for the speedy fix, I will test this is working again next week and let you know if I have issues!!
Using version 3.29.0 works for me.
RN 0.68.2
This issue persists for me in v3.31.1 (react-native v0.71.x)