[Fabric] Build failed after upgrade to 3.12.0 (explained)
See original GitHub issueOn Android i am getting this error while building
FYI: I just added newArchEnabled=true
as mentioned in the docs, in the gradle.properties
.
Now after cleaning and reinstalling the newer version i am getting this error.

On IOS i enabled fabric inside podfile by adding this flag :fabric_enabled => true
and added react-native-codegen in my node modules but now when i try to install pods with this command RCT_NEW_ARCH_ENABLED=1 pod install
i am getting this error.

Any solution to fix these will be appreciated, thanks.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:9 (3 by maintainers)
Top Results From Across the Web
Fabric error while updating game from 1.18.1 to 1.18.2 - Support
Hi guys. I was recently updating my game from 1.18.1 to 1.18.2. I'm using fabric 0.13.3 and I'm getting an error that I'm...
Read more >gradle build fails after upgrade? - spring boot - Stack Overflow
I have a gradle file that worked for quite some time until apparently the gradle on my OS X was updated (just guessing,...
Read more >Jenkins Plugins Javadoc
Build Failure Analyzer2.4.0. build-failure-analyzer ... Changes since last successful build0.6 ... commons-lang3 v3.x Jenkins API3.12.0-36.vd97de6465d5b_.
Read more >What's New | Oracle, Software. Hardware. Complete.
Packages Released on Oracle Linux Yum Server · xrdp-0.9.21-1.el9 - Open source remote desktop protocol (RDP) server (Update) · voms-api-java-3.3.2-11. · rust- ...
Read more >Develop Hyperledger Fabric Chaincode Using Java on ...
The following is a high-level summary of the steps to install and run Java ... Java chaincode steps on Managed Blockchain: build, install,...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
As this topic is quite confusing I’ll pin this issue for others to see. Also, this definitely needs to be better explained in READMEs.
I am on 3.15.0; getting the same error; which is weird since I never got it before. tried all kind of delete node_modules / clearing cache / restarting the computer etc, without luck.
Did you manage to find a solution? 😃