Today we’re releasing React Native v0.66 for Android 12 and iOS 15 support alongside fixes and general updates.
- Handle taps on views outside parent bounds on Android
- New Bluetooth Permissions on Android
- Better Support for Apple Silicon, Xcode 13, and iOS 15
- Hermes 0.9.0
- Nightly and “Commitly” Releases
Handle taps on child views outside parent boundaries on Android
Thanks to @hsource for adding interaction support for children rendered outside of parent view boundaries via
overflow: visible. This is a common use-case and aligns React Native on Android more closely with web standards.
Find more details on the pull request.
New Bluetooth Permissions on Android
We’ve added support for new Bluetooth permissions in preparation for Android 12 and we plan to update the
targetSDKVersion to 31 in the next release.
Better Support for Apple Silicon, Xcode 13, and iOS 15
This release provides a number of solutions to make Xcode builds for iOS on Apple Silicon (M1) Mac machines more reliable.
Notably, the new app template now includes a CocoaPods workaround (thanks to @mikehardy!).
To apply, make sure your app’s Podfile has
__apply_Xcode_12_5_M1_post_install_workaround(installer) added in the
RCT-Folly.podspec has been updated to prevent arm64 linker failure.
Check out this post we shared on preparing your app for iOS 15 and Android 12.
Hermes 0.9.0 is primarily about closing the gap between Hermes release cut point and this React Native release.
Among ~400 commits, there have been general bug fixes alongside memory and size wins.
See Hermes 0.9.0 release issue for more details
Nightly and “Commitly” Releases
In a recent blog post we shared that one of our goals in the second half of 2021 is to improve our release process to be faster and more stable. As part of this effort we are working to make React Native more stable on main and to reduce the bugs identified during our Release Candidate process.
While we have been publishing nightly releases of React Native for over a year, these releases haven’t been effectively used by most projects. They are now easier to access and we hope to use them as release candidates going forward. Nightly releases are published to npm under the “nightly” tag.
To improve the process of testing individual commits, React Native’s CI will now create a tarball artifact for each commit on the main and release branches as well as for each PR. We refer to them as commitlies. These commitlies will not be published to npm, but they can be downloaded directly from CircleCI. See instructions below.
Want to help get a PR merged? By trying out the related commitly and verifying the change, you will be providing valuable signal to help get the change landed!
Using Nightly Releases (Nightlies)
The process for migrating your project to a React Native nightly release is very similar to the one you would follow when upgrading to a regular version, with the exception that tools like the Upgrade Helper do not currently work with nightlies. With that in mind, we recommend that you first upgrade your project to the most recent stable release if you have not done so yet. Then, run
yarn upgrade react-native@nightly to install the most recent nightly release. Note that there may be additional changes that are needed for your project to work properly on a nightly release.
Using Commitly Releases (Commitlies)
Just like with a nightly release, first make sure that your project has been upgraded to the most recent stable version. Then, go to the
react-native dashboard on Circle CI and look up the workflow that was triggered by the commit in question. There, you should see a job named
build_npm_package. That job will have an “Artifacts” panel which will provide a link that you may use to download a tarball file. You can then run the following:
# Update your react-native dependency to the tarball
# using your preferred package manager
$ yarn add <path to tarball>
$ npm add <path to tarball>
This release includes 621 commits with 92 contributors! Thank you to all our contributors new and old! You can find the full changelog here.
As well, thank you to the following contributors for their support in preparing, testing and unblocking this release!