React Native - Tips

(how to) set application icon badge number



not supported natively - use 3rd party libraries like ShortcutBadger.

though not all Android launchers are supported (not all launchers support showing application icon badger number at all) - e.g. badge number is not set on application icon in emulator (Nexus 5X) with the following error in device system log (adb logcat):

Caused by: me.leolin.shortcutbadger.ShortcutBadgeException:
  unable to resolve intent: Intent { act=android.intent.action.BADGE_COUNT_UPDATE (has extras) }


  1. PushNotificationIOS

supported natively - see the link for how to link PushNotificationIOS native library manually.

universal solution

use react-native-push-notification RN package which:

(how to) dismiss keyboard when tapping outside of TextInput


by default keyboard is not dismissed when tapping outside of TextInput - wrap the latter in ScrollView for this to happen:

<ScrollView keyboardShouldPersistTaps='handled'>
    onChangeText={value => this.setState({search: value})}

if there is a ListView somewhere below you’ll have to wrap ScrollView in View - otherwise it’s not visible.

(how to) dismiss keyboard when pressing <CR> on keyboard


(how to) open application in store


first find out application IDs in the App Store and the Google Play Store:

examples of application IDs:

examples of final URLs:

since iOS 9 it’s necessary to allow to query schemas explicitly in Info.plist or else canOpenUrl will always return false.

install react-native-app-link package to handle it for you:

$ npm install --save react-native-app-link

NOTE: still opening application in the App Store doesn’t work in emulator.

process invalid props for all mounted components

I had one component (TeamInfoPage) pushed on top of another one (TeamPage) using navigator - the 1st component is not unmounted in this case.

it has turned out that TeamPage component is still updated in the background.

so make sure to allow for invalid properties in hidden component caused by some action in pushed component (in my case team was destroyed in TeamInfoPage and I had to process undefined team in TeamPage component).

don’t return null from top level component’s render method

in my case returning null from top level component (i.e. component rendered right in App.js for specified route) caused application to crash.


well, I can’t reproduce it now - returning null just hides component. according to docs returning null used to be not supported in the past but that’s no longer the case.

so just be cautious when returning null - if it breaks anything, return, say, Text instead.

log error messages in catch clauses

in case of unhandled promise rejection there might be no relevant messages in react-native log-ios output - make sure errors are logged in corresponding catch clauses in that case.

(how to) to use absolute paths for imports


the problem is that it’s necessary to include application directory name if you want to use absolute paths:

import MyComponent from '<APP_DIR>/app/components/MyComponent';

it’s possible to use babel-plugin-root-import plugin but Vim’s gf command (opens file under the cursor) doesn’t understand its notation (~ stands for <APP_DIR>/app by default).

the solution is to create package.json in directory from which you want to import (it’s app/ as a rule):

  "name": "app"

this name can then be used when importing modules:

import MyComponent from 'app/components/MyComponent';

in fact the name can be anything (say, app1) but for Vim to find the file being imported it must match application top-level directory name (app) - that’s the whole point of using custom name instead of ~ prefix.

behaviour of nested ScrollViews

ScrollView is scrollable if scrollEnabled={true} (default value).

ScrollView 1 (scrollable)
  ScrollView 2 (not scrollable)
    ScrollView 3 (scrollable)

=> ScrollView 3 scrolls inside of ScrollView 2.

ScrollView 1 (scrollable)
  ScrollView 2 (scrollable)
    ScrollView 3 (scrollable)

=> ScrollView 3 doesn’t scroll inside of ScrollView 2 but they scroll together inside ScrollView 1.

but in general it’s better to avoid nested ScrollViews.

(how to) add comments inside JSX

  {/* some comment... */}

(how to) add newline inside Text


(how to) add whitespace (not NBSP) inside Text

  click <Text>"this link"</Text>

(how to) make animations smooth


fetching data in the background might prevent animations from running smoothly so schedule fetching data after all interactions have completed (animations are interactions as well):

import {InteractionManager} from 'react-native';

export default class ShowPage extends React.Component {
  state = {
    interactionsComplete: false,

  componentDidMount() {
    InteractionManager.runAfterInteractions(() => {
      Promise.all([this.props.getGame(), this.props.getGameStat()])
        .then(() => this.setState({interactionsComplete: true}))

  render() {
    if (!this.state.interactionsComplete) {
      return <IndicatorHOC />;
    // ...

(how to) disable keyboard for not editable TextInput

on Android keyboard pops up when not editable TextInput is tapped.

in my case this was caused by focusing TextInput on each tap manually (it’s wrapped into TouchableWithoutFeedback to extend tappable area):

render () {
  return (
    <TouchableWithoutFeedback onPress={this._handlePress}>
      <View style={this._containerStyle()}>

// this._textInput is a ref to TextInput
_handlePress = () => {

solution is to disable focusing not editable TextInput:

  _handlePress = () => {
+   if (!this.props.editable) { return; }

not editable TextInput itself doesn’t receive touch events.

(how to) handle press on not editable TextInput

<TouchableOpacity onPress={this._handlePress}>
  <View pointerEvents='none'>
    <TextInput editable={false} />

it’s required to add proxy View with pointerEvents='none' - otherwise _handlePress callback is not even called.

numberToCurrency helper