react-native: C++ exception in 'nativeFlushQueueImmediate'

Is this a bug report?

YES

Have you read the Contributing Guidelines?

YES

Environment

react-native -v: 0.47.1
node -v: 2.0.1
npm -v: 5.3.0

Then, specify:

Target Platform: IOS

Development Operating System: Mac El-Capitan

Build tools: Xcode

Steps to Reproduce

(Write your steps here:)

The below errors keep coming up randomly when I try to navigate to a screen. I use react native navigation.

Expected Behavior

The errors should not show up randomly

Actual Behavior


Sep 18 18:36:28 assertiond[24518]: assertion failed: 15G1108 13A344: assertiond + 12188 [93893311-6962-33A7-A734-E36F946D8EBA]: 0x1
Sep 18 18:36:29 --- last message repeated 1 time ---
Sep 18 18:36:29  AppName[28907]: C++ exception in 'nativeFlushQueueImmediate'
  
  Did not get valid calls back from JS: [[78,31],[1,0],[[365,100,1505739989356,false]],3027]
Sep 18 18:36:29  AppName[28907]: Unhandled JS Exception: C++ exception in 'nativeFlushQueueImmediate'
  
  Did not get valid calls back from JS: [[78,31],[1,0],[[365,100,1505739989356,false]],3027]
Sep 18 18:37:00  routined[24502]: CoreLocation: Error occurred while trying to retrieve motion state update: CMErrorDomain Code:104x

Reproducible Demo

There is no predictible way to reproduce this. It just occurs at random on screen navigation.

(Paste the link to an example project and exact instructions to reproduce the issue.)

About this issue

Original URL
State: closed
Created 7 years ago
Reactions: 35
Comments: 16

Most upvoted comments

I was also experiencing a similar issue with a component as screen title. What I found out is that react-navigation was trying to use that same component as a text for the back button, something that is actually not possible.

The workaround I’ve found is setting navigationOptions.headerBackTitle explicitly on the screen that triggers the navigation. FYI, I’ve reported my issue here

+24

albertogasparin on Nov 24, 2017

im having this problem too, using react-navigation, navigating to another screens we are using setParams (if that helps to debugging)

mersay on Nov 14, 2017

I get this error when I’m uploading images to S3

2017-11-13 13:05:41.696 [warn][tid:com.facebook.react.JavaScript] Possible Unhandled Promise Rejection (id: 0):
Error: C++ exception in 'nativeFlushQueueImmediate'

Malformed calls from JS: field sizes are different.

[[58,58,58,58,58,58,15,27],[4,4,4,4,4,4,1,0],[[1],[1],[1],[1],[1],[1],[136,100,1510545939677,false]],5224]
nativeFlushQueueImmediate@[native code]

hkung77 on Nov 13, 2017

I observed nativeFlushQueueImmediate C++ exception error on Android emulator

Environment react-native-cli: 2.0.1 react-native: 0.55.4 node -v: v8.11.3 yarn -v: 1.7.0 npm -v: 6.2.0

Target Platform: Android Development Operating System: Mac High Sierra Build tools: Android studio (3.1.3) > AVD > Emulator (Nexus 5x API 28)

These are two different stack traces of actual issue:

screenshot_1533571998

screenshot_1533573129

hisavali on Aug 6, 2018

I found some condition which produce same bug:

<View style={[styles.container, { opacity: this.birdOpacity }]}>

bird opacity is dynamically changes by time and it’s Animated.Value. I forgot to change View to Animated.View which produces this bug.

suchcodemuchwow on Mar 31, 2018