-
Notifications
You must be signed in to change notification settings - Fork 63
Make versions consistent and bump fbjni to 0.3.0 #458
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Here are the build results |
Apps/PackageTest/0.69.0/android/gradle/wrapper/gradle-wrapper.properties
Outdated
Show resolved
Hide resolved
As a NIT comment. The root README file mentions the NDK version 21.3.6528147 which should be updated to 21.4.7075529 with this change. |
I added a documentation section to the description to update the README once we settle on a version. |
- buildToolsVersion - compileSdkVersion - targetSdkVersion - gradle maven dependency - gradle distribution
Here are the build results |
Here are the build results |
Here are the build results |
Here are the build results |
…)" This reverts commit f6e168d.
This change fixes a runtime problem when integrating Babylon React Native with an NDK greater than r21b. The symptom for this change is that some devices will crash with the following error:
Main Change
Consistency Changes
Additional Details
It all started from the following NDK change: https://github.com/android/ndk/wiki/Changelog-r21#r21b
Early version of NDK r21, the unwinder symbols were exposed, but was later fixed in r21b. This make it such that any
.so
libraries compiled with r21 be incompatible with libraries compiled with r21b or greater. See this.This also includes any
.so
dependencies that uses the NDK, which seems obvious now, but it wasn't when we were investigating. This means that our only dependency that also must be updated isfbjni
, which is the main fix for this change. I also updated version numbers to be consistent across the different cases because it was confusing what version we are actively using in the code base.Documentation
Testing
Other
Just for completeness, here are some documentation links (thanks to @bbowman) that were useful while investigating this issue: