Today we’re releasing React Native version 0.62 which includes support for Flipper by default.

This release comes in the midst of a global pandemic. We’re releasing this version today to respect the work of hundreds of contributors who made this release possible and to prevent the release from falling too far behind master. Please be mindful of the reduced capacity of contributors to help with issues and prepare to delay upgrading if necessary.

Flipper by default

Flipper is a developer tool for debugging mobile apps. It’s popular in the Android and iOS communities, and in this release we’ve enabled support by default for new and existing React Native apps.

Flipper provides the following features out of the box:

Metro Actions : Reload the app and trigger the Dev Menu right from the toolbar.

: Reload the app and trigger the Dev Menu right from the toolbar. Crash Reporter : View crash reports from Android and iOS devices.

: View crash reports from Android and iOS devices. React DevTools : Use the newest version of React DevTools right alongside all your other tools.

: Use the newest version of React DevTools right alongside all your other tools. Network Inspector : View all of the network requests made by device applications.

: View all of the network requests made by device applications. Metro and Device Logs : View, search, and filter all logs from both Metro and the Device.

: View, search, and filter all logs from both Metro and the Device. Native Layout Inspector : View and edit the native layout output by the React Native renderer.

: View and edit the native layout output by the React Native renderer. Database and Preference Inspectors: View and edit the device databases and preferences.

Additionally, since Flipper is an extensible platform, it provides a marketplace that pulls plugins from NPM so you can publish and install custom plugins specific to your workflows. See the available plugins here.

For more information, check out the Flipper documentation.

New dark mode features

We’ve added a new Appearance module to provide access to the user's appearance preferences, such as their preferred color scheme (light or dark).

const colorScheme = Appearance . getColorScheme ( ) ; if ( colorScheme === 'dark' ) { }

We’ve also added a hook to subscribe to state updates to the users preferences:

import { Text , useColorScheme } from 'react-native' ; const MyComponent = ( ) => { const colorScheme = useColorScheme ( ) ; return < Text > useColorScheme(): { colorScheme } </ Text > ; } ;

See the docs for Appearance and useColorScheme for more information.

Moving Apple TV to react-native-tvos

As part of our Lean Core effort and to bring Apple TV in line with other platforms like React Native Windows and React Native macOS, we’ve started to remove Apple TV specific code from core.

Going forward, Apple TV support for React Native will be maintained in react-native-community/react-native-tvos along with the corresponding react-native-tvos NPM package. This is a full fork of the main repository, with only the changes needed to support Apple TV.

Releases of react-native-tvos will be based on the public release of React Native. For this 0.62 release of react-native please upgrade Apple TV projects to use react-native-tvos 0.62.

More upgrade support

When 0.61 was released, the community introduced a new upgrade helper tool to support developers upgrading to new versions of React Native. The upgrade helper provides a diff of changes from the version you're on to the version you're targeting, allowing you to see the changes that need to be made for your specific upgrade.

Even with this tool, issues come up when upgrading. Today we're introducing more dedicated upgrading support by announcing Upgrade-Support. Upgrade Support is a GitHub issue tracker where users can submit issues specific to upgrading their projects to receive help from the community.

We're always working to improve the upgrade experience, and we hope that these tools give users the support they need in the edge cases we haven't covered yet.

Other improvements

LogBox : We’re adding the new LogBox error and warning experience as an opt-in; to enable it, add require('react-native').unstable_enableLogBox() to your index.js file.

: We’re adding the new LogBox error and warning experience as an opt-in; to enable it, add to your file. React DevTools v4 : This change includes an upgrade to the latest React DevTools which offers significant performance gains, an improved navigation experience, and full support for React Hooks.

: This change includes an upgrade to the latest React DevTools which offers significant performance gains, an improved navigation experience, and full support for React Hooks. Accessibility improvements: We’ve made improvements to accessibility including adding accessibilityValue, missing props on Touchables, onSlidingComplete accessibility events, and changing the default role of Switch component from "button" to "switch" .

Breaking changes

Remove PropTypes : We're removing propTypes from core components in order to reduce the app size impact of React Native core and to favor static type systems which check at compile time instead of runtime.

: We're removing from core components in order to reduce the app size impact of React Native core and to favor static type systems which check at compile time instead of runtime. Remove accessibilityStates : We’ve removed the deprecated accessibilityStates property in favor of the new accessibilityState prop which is a more semantically rich way for components to describe information about their state to accessibility services.

: We’ve removed the deprecated property in favor of the new prop which is a more semantically rich way for components to describe information about their state to accessibility services. TextInput changes: We removed onTextInput from TextInput as it’s uncommon, not W3C compliant, and difficult to implement in Fabric. We also removed the undocumented inputView prop, and selectionState .

Deprecations

AccessibilityInfo.fetch was already deprecated, but in this release we added a warning.

was already deprecated, but in this release we added a warning. Setting useNativeDriver is now required to support switching the default in the future.

is now required to support switching the default in the future. The ref of an Animated component is now the internal component and deprecated getNode .

Thanks

Thank you to the hundreds of contributors that helped make 0.62 possible!

To see all the updates, take a look at the 0.62 changelog.