Join GitHub today
0.60.x Discussion #99
Please note that we haven't cut 0.60-stable branch yet.
The latest release candidate is 0.59.0-rc.3. You can track it's progress here: #79
This thread is to inform you when next release candidate is going to happen. We are checking whether there is any "work-in-progress" that we should be aware of and wait before we make a next Release Candidate.
The plan is to release 0.60.0-rc.0 this week.
Google mandates 64-bit support for apps starting 2019-08, so to meet that React-Native started specifying the 64-bit ABIs, and then included an updated JSC. Each of those increased the size a lot, but mostly in the per-ABI parts of the APK.
You'll want to generate per-ABI APKs for Google to serve so that your end users only download the ABI they need - meaning your actual end-user downloads might be something like 30% of the size of what you see in the universal debug APKs.
The output of 'react-native init' produces a Gradle file that seems to implement this so when you do an android release build there should be multiple variants generated, at least one for each ABI.
You add each of those to your app release on the Play Store and Google will deliver the right one to the user.
And if I'm wrong in any way someone please correct me of course :-). Cheers.
Thanks @mikehardy and @guhungry,
Please cherry-pick facebook/react-native@d4aa1e7, as it contains a fix for an issue introduced in facebook/react-native@d2153fc#diff-a1e6ca3a6b1647be95d97e7890bcc11c that affects devices using Android API < 26.
referenced this issue
Mar 15, 2019
Hey everyone - we have reached a decision on our approach to the releases (you can read the details here).
Related to it, we have decided to postpone the release of 0.60 of around a couple weeks: we will remove the current 0.60 branch and re-cut it in the near future. We'll open a new issue once it's cut, in order to focus on improving 0.59 in the meantime.