React-native: Bridge extractArgument: doubleValue() on a null object reference

[tapz]

• [X] I have reviewed the documentation
• [X] I have searched existing issues
• [X] I am using the latest React Native version

I got this to Crashlytics from one of the users of my app. Would be nice to get more information and the actual cause of the error.

Fatal Exception: java.lang.NullPointerException: Attempt to invoke virtual method 'double java.lang.Double.doubleValue()' on a null object reference
       at com.facebook.react.bridge.ReadableNativeArray.getDouble(ReadableNativeArray.java:114)
       at com.facebook.react.bridge.JavaMethodWrapper$4.extractArgument(JavaMethodWrapper.java:64)
       at com.facebook.react.bridge.JavaMethodWrapper$4.extractArgument(JavaMethodWrapper.java:60)
       at com.facebook.react.bridge.JavaMethodWrapper.invoke(JavaMethodWrapper.java:359)
       at com.facebook.react.bridge.JavaModuleWrapper.invoke(JavaModuleWrapper.java:160)
       at com.facebook.react.bridge.queue.NativeRunnable.run(NativeRunnable.java)
       at android.os.Handler.handleCallback(Handler.java:789)
       at android.os.Handler.dispatchMessage(Handler.java:98)
       at com.facebook.react.bridge.queue.MessageQueueThreadHandler.dispatchMessage(MessageQueueThreadHandler.java:29)
       at android.os.Looper.loop(Looper.java:164)
       at com.facebook.react.bridge.queue.MessageQueueThreadImpl$3.run(MessageQueueThreadImpl.java:192)
       at java.lang.Thread.run(Thread.java:764)

Environment

Environment:
OS: macOS High Sierra 10.13.4
Node: 8.11.1
Yarn: 1.6.0
npm: 5.6.0
Watchman: 4.9.0
Xcode: Xcode 9.3.1 Build version 9E501
Android Studio: 3.1 AI-173.4697961

Packages: (wanted => installed)
react: 16.3.2 => 16.3.2
react-native: 0.55.4 => 0.55.4

Steps to Reproduce

No idea.

Expected Behavior

No crash

Actual Behavior

Crash

[react-native-bot]

We use GitHub Issues exclusively for tracking bugs in React Native. See the React Native Community Support page for a list of places where you may ask for help.

[coderdave]

This IS a bug. Why was it closed?

I've attached the red screen if that helps. I also noticed that it happens more often when I navigate quickly around the app.

[tapz]

This is a React Native issue. It has something to do with the bridge, state changes and updating the UI. I changed the order in which I set the state and call native methods and the error does not occur anymore.

[tapz]

Anything I did in my code had nothing to do with any double argument. So clearly some screen drawing issue in RN.

[pilot4u]

I'm having the same issue while executing this method:
https://reactnavigation.org/docs/en/navigating-without-navigation-prop.html
and navigating within componentWillReceiveProps

[bondansebastian]

Hi @tapz , i'm having the same issues as everyone here
Can you elaborate more what do you mean by

I changed the order in which I set the state an call native methods

[tapz]

Hi @bondansebastian , I modified my code to change the component state in one place instead of setting different fields separately. Also moved the calls to native bridge to different places. Can't really tell any systematic way. Just doing things differently seems to have bypassed the bug.

[witalobenicio]

Also moved the calls to native bridge to different places

What do you mean by this @tapz ?

[mjugger]

@tapz
Can you give us a code example of what you mean?

[mjugger]

So far this error only seems to happen when I use hot reload

[seanmorton]

I'm seeing this error in release mode, so likely not just related to hot reload. I'm on RN 0.56.0.

[jnrepo]

I'm also seeing this in release mode w/ Android. Using react-native 0.55.3.

[gluons]

I also face this problem.

@tapz Can you reopen this issue?

[gluons]

I found the solution for my problem. My fault. 😅 🤦‍♀

I forget to give a second parameter (duration) to ToastAndroid.show.

[seanmorton]

For me, this was also an issue with my own codebase. No need to reopen.

[noahtallen]

I'm trying to use StatusBar.setBackgroundColor(color, true) and getting this error. Only reason I'm using imperative API is because the status bar component isn't working for one specific component for some reason.

[tuononh]

@ntomallen Have you solve it? I have the same problem. Others StatusBar methods work fine.

[noahtallen]

I stopped trying to use that method. I think it was set incorrectly on the android side of things; maybe in the manifest

[im-aditya]

Having the same issue.

[serhiipalash]

I have this error when I pass NaN to animatedScale.setValue(newScale). If anyone else is experiencing this issue during animation handling, check your calculation so that new value always should be a real number.