requestIdleCallback crashing on Android app launch (mReactChoreographer)

Problem

When requestIdleCallback is called outside of a Component at start, such as prior to AppRegistry getting called, results in an assertion failure within Timing.java (line 287). This is due to mReactChoreographer being null inside Timing#setChoreographerIdleCallback, because it is being executed prior to Timing#initialize is getting called (which sets mReactChoreographer by retrieving the singleton).

This error can be replicated with this index.android.js:

import React, {Component} from 'react'
import {AppRegistry, Text} from 'react-native'

requestIdleCallback(() => console.log('If this works, it\'s not broken :)')) // This will trigger the force close

AppRegistry.registerComponent('Broken App', () => () => <Text>Hello</Text>)

Related

requestIdleCallback was implemented on Android in this PR https://github.com/facebook/react-native/pull/8569. I don’t believe that it has been updated since (as far as I could tell from a quick diff b/w v0.31 and master).

Environment

• React Native: 0.31
• Dev OS: macOS
• App Environment: Android Emulator, Intel x64, 6.0

[janicduplessis]

@awendland Thanks for the detailed report, I’ll take a look at it soon.

[brentvatne]

https://snack.expo.io/SJNxdKDAb @idibidiart