Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

C++ exception in 'nativeFlushQueueImmediate'

See original GitHub issue

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.)

Issue Analytics

State:
Created 6 years ago
Reactions:35
Comments:16

Top GitHub Comments

24reactions

albertogasparincommented, Nov 24, 2017

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

7reactions

mersaycommented, Nov 14, 2017

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

Top Results From Across the Web

C++ exception in 'nativeFlushQueueImmediate' when ...

This can happen when you've updated a native dependancy via npm but have not rebuilt the native side of your app.

Exception Handling in C++: When to avoid exceptions

The best advice for deciding when to use exceptions is to throw exceptions only when a function fails to meet its specification. Not...

A brand new website interface for an even better experience!

iOS - C++ Exception in 'nativeFlushQueueImmediate'

Exceptions

Exceptions provide a way to react to exceptional circumstances (like runtime errors) in programs by transferring control to special functions called handlers.

Change Log

android: add callback for save dom node exception (8c0078e); android: fix library symbol ... core: fixed nativeFlushQueueImmediate callID issue (ea77912) ...