So everybody that works with React Native probably know the frustration. Everything was working fine and all of a sudden the project doesn't built anymore. Most of the times it breaks on gradlew assembleRelease.
How is this even possible? It happened to me over the course of the last few years over and over again. Litterally no changes, and boom, random errors. Most of the times you trace the error to some question on stackoverflow and you apply some random fix, downgrade of libraries e.t.c.
But my question is: why does this even happen in the first place? Does react-native / gradle auto update stuff? Sometimes when I run from Android Studio I notice in the status bar that Gradle seems to download/sync a lot of stuff.
How can you work reliable on software if it breaks out of nowhere? My most recent example is this one. From my github repo I know for sure there has not been a single change.
My most recent example? This one. The person that asked the question is saying the same. Changed nothing, and project breaks. More than one file was found with OS independent path 'lib/armeabi-v7a/libfbjni.so'
Off course people come up with solutions, such as upgrade your RN to a patch version. But no one seems to answer the most obvious question; why and how does this even break in the first place when no changes are made?
Off course people come up with solutions, such as upgrade your RN to a patch version. But no one seems to answer the most obvious question; why and how does this even break in the first place when no changes are made?
