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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
APK file is larger with react-native 0.59 #24154
Comments
This is expected. With 0.59 we shipped a new version of JSC which is both a ton faster and 64-bit compatible. Unfortunately for now we have to live with the size increase but we are working on removing several modules from React Native at the moment: #23313. |
I completly understand that the addition of JSC make APK file larger than before but is it normal that both libjsc.so and libc++_shared.so are huge compare to the other '.so' in the APK ? |
did you find information about that? the increase in size does not seem reasonable. BTW in my case it is 9.6MB and 4.6MB respectively. |
Our app size increased by about 7MB. If the increase is similar for others, I see a lot of people sticking with |
@sridhar-vadlamani-ck Do you splits your application into multiple APK ? Splitting you app into an APK for each architecture could reduce that increase. |
@Thebarda good point, i will do a comparison and see how much increase we are getting |
We are seeing a similar size increase (around 4 MB for us) after upgrading from React Native 0.57.8 to 0.59.5. Comparing, for instance, |
How can we strip these ourselves if we build from source ? |
馃悰 Bug Report
After building my arm APK, I noted that APK file increased by about 3 MB.
With Android Studio, I analyzed that APK I found two unstripped .so files, libjsc.so and libc++_shared.so, they respectively size 12.7MB and 5.7MB.
To Reproduce
npm install
then
unzip -l node_modules/react-native/android/com/facebook/react/react-native/0.59.2/react-native-0.59.2.aar
Expected Behavior
These two files must be stripped to reduce their size and, so, to reduce APK file size.
Code Example
Environment
The text was updated successfully, but these errors were encountered: