React Native Android error in com.facebook.react.bridge.NoSuchKeyException

Question

I'm getting an error caught by Crashlytics and it's happening to almost 45% of the users but it doesn't seem to happen when the user is using the app but when it's in the background.

The stacktrace shown on Crashlytics is:

Fatal Exception: com.facebook.react.bridge.NoSuchKeyException ReadableNativeMap.java:124 lineNumber

I have no clue what can be causing this issue, if it's a Javascript error or a native library error

Noticing the same exception since today. react-native: 0.56.0, react-native-fbsdk: 0.8.0 — Sebastian Auberger
– Sebastian Auberger, Commented Apr 8, 2019 at 15:03
Same error on react-native 0.59.3, I believe some module should be blamed — Alexey Chernikov
– Alexey Chernikov, Commented Apr 9, 2019 at 21:32
Here is the bug report: github.com/facebook/react-native/issues/24382 — Sebastian Auberger
– Sebastian Auberger, Commented Apr 12, 2019 at 7:12

Francois Nadeau · Accepted Answer · 2019-07-16 13:38:45Z

6

This is a problem caused by the stacktrace-parser library which is used internally by react native. Basically, release 0.1.4 works fine while releases 0.1.5 and 0.1.6 causes the lineNumber error.

Do the following to fix this:

If you are using yarn add the following to your package.json:

  "resolutions": {
    "stacktrace-parser": "0.1.4"
  },

if you are using npm add the following to your package.json:

"dependencies": {
    ...
    "stacktrace-parser": "0.1.4"

Remove the yarn.lock (or package-lock.json) file and the node_modules directory.
Install the packages yarn install (or npm install)
Rebuild your release build.

I hope this helps others until the library gets fixed.

edited Jul 16, 2019 at 13:38

answered May 23, 2019 at 13:37

Francois Nadeau

7,4932 gold badges55 silver badges59 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

Francois Nadeau Over a year ago

No, I have not tried with 0.1.8, but I am sure that they will solve the problem eventually. Once they do this answer will become obsolete. :)

Jordan Daniels · Accepted Answer · 2019-07-14 18:39:11Z

1

My solution was to remove every console.error in my project.

https://github.com/facebook/react-native/issues/24382

answered Jul 14, 2019 at 18:39

Jordan Daniels

5,3241 gold badge23 silver badges29 bronze badges

Comments

Masuk Helal Anik · Accepted Answer · 2019-04-08 15:06:40Z

0

Make sure "backgroundColor" value is never null or undefined. In my case that was the reason.

answered Apr 8, 2019 at 15:06

Masuk Helal Anik

2,28624 silver badges31 bronze badges

2 Comments

Thiago Nascimento Over a year ago

Do you know anyway I can reproduce thismissue locally, because it seems to be happening when the app is in background?

Masuk Helal Anik Over a year ago

In my case, the crash also happened when the app is in background

Thiago Nascimento · Accepted Answer · 2019-04-16 02:50:52Z

-2

It ended up being an issue with some native library that was causing the crash. Simply upgrading it solved the problem

answered Apr 16, 2019 at 2:50

Thiago Nascimento

1,1552 gold badges18 silver badges40 bronze badges

3 Comments

Bishnu Pada Chanda Over a year ago

which native library? you should have mention that.

Pollizzio Over a year ago

This answer is not useful, you should change to Francois's answer to be the accepted one

mosabbir tuhin Over a year ago

facing this problem for android os 4, after i migrated codebase from rn 0.59.9 to 0.60.5, can you mention which library causes the crash?

Collectives™ on Stack Overflow

React Native Android error in com.facebook.react.bridge.NoSuchKeyException

4 Answers 4

1 Comment

Comments

2 Comments

3 Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

4 Answers 4

1 Comment

Comments

2 Comments

3 Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related