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.

_RNGestureHandlerModule.default.Direction in react native 0.60.0

See original GitHub issue

I have used the following configurations.

    "react": "16.8.6",
    "react-native": "0.60.0",
    "react-native-gesture-handler": "^1.3.0",
    "react-navigation": "^3.11.0",
    "react-navigation-fluid-transitions": "^0.3.2"

In react-native latest version 0.60.0, facing an issue.

Issue Analytics

State:
Created 4 years ago
Reactions:2
Comments:10 (1 by maintainers)

Top GitHub Comments

21reactions

hellotobycommented, Jul 8, 2019

Looks like this is to do with the new autolinking feature in RN 0.60. To fix for now just add the following podspec for RNGesureHandler to ios/Podfile

pod 'RNGestureHandler', :podspec => '../node_modules/react-native-gesture-handler/RNGestureHandler.podspec'

Then in the ios directory run pod install to install it.

3reactions

godestedcommented, Jul 7, 2019

After build I catch two errors

Unhandled JS Exception: null is not an object (evaluating '_RNGestureHandlerModule.default.Direction')

RCTFatal
-[RCTExceptionsManager reportFatalException:stack:exceptionId:]
__invoking___
-[NSInvocation invoke]
-[NSInvocation invokeWithTarget:]
-[RCTModuleMethod invokeWithBridge:module:arguments:]
facebook::react::invokeInner(RCTBridge*, RCTModuleData*, unsigned int, folly::dynamic const&)
facebook::react::RCTNativeModule::invoke(unsigned int, folly::dynamic&&, int)::$_0::operator()() const
invocation function for block in facebook::react::RCTNativeModule::invoke(unsigned int, folly::dynamic&&, int)
_dispatch_call_block_and_release
_dispatch_client_callout
_dispatch_lane_serial_drain
_dispatch_lane_invoke
_dispatch_workloop_worker_thread
_pthread_wqthread
start_wqthread

And

Module AppRegistry is not a registered callable module (calling runApplication)

callFunctionReturnFlushedQueue
    [native code]:0

Sometimes build does not throw any errors, but after first click I getting this one

Module RCTEventEmitter is not a registered callable module (calling receiveTouches)

__callFunction
    index.bundle?platform=ios&dev=true&minify=false:2227:18
<unknown>
    index.bundle?platform=ios&dev=true&minify=false:1971:31
__guard
    index.bundle?platform=ios&dev=true&minify=false:2183:15
callFunctionReturnFlushedQueue
    index.bundle?platform=ios&dev=true&minify=false:1970:21
callFunctionReturnFlushedQueue
    [native code]:0

Dependencies


    "react": "16.8.6",
    "react-native": "0.60.0",
    "react-native-gesture-handler": "^1.3.0",
    "react-navigation": "^3.11.0"

Top Results From Across the Web

null is not an object (evaluating '_RNGestureHandlerModule ...

Show activity on this post. Looks like this is to do with the new autolinking feature in RN 0.60 . Then in the...

null is not an object (evaluating 'agorartcchannelmodule.prefix')

I would first check when that function is being called. I suspect you will be surprised at when it's happening. e.g. perhaps it's...

Troubleshooting - React Navigation

Error: While trying to resolve module "@react-navigation/native" from file ... an error "null is not an object (evaluating 'RNGestureHandlerModule.default.

react-native-gesture-handler - npm

Experimental implementation of a new declarative API for gesture handling in react-native. Latest version: 2.8.0, last published: 2 months ...

rngesturehandlermodule.default.direction react native

visit :- https://software-mansion.github.io/react-native-gesture-handler/docs/getting-started.html.