CODEWITHSUNDEEP
androidreactjsreact-native
Thiago Nascimento
Thiago Nascimento

Reputation: 1155

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

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

Upvotes: 13

Views: 16375

Answers (4)

Francois Nadeau
Francois Nadeau

Reputation: 7463

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:

  1. 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"
  1. Remove the yarn.lock (or package-lock.json) file and the node_modules directory.
  2. Install the packages yarn install (or npm install)
  3. Rebuild your release build.

I hope this helps others until the library gets fixed.

Upvotes: 6

Jordan Daniels
Jordan Daniels

Reputation: 5304

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

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

Upvotes: 1

Thiago Nascimento
Thiago Nascimento

Reputation: 1155

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

Upvotes: -2

Masuk Helal Anik
Masuk Helal Anik

Reputation: 2283

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

Upvotes: 0

Related Questions