Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

'Node module cannot be null' error #30

Closed
TaiWilkin opened this issue Jun 25, 2017 · 7 comments
Closed

'Node module cannot be null' error #30

TaiWilkin opened this issue Jun 25, 2017 · 7 comments

Comments

@TaiWilkin
Copy link

After adding this, I got the error 'Node module cannot be null'. Stack trace mentions Tts.NativeEventEmitter as the error source. I don't get the error if I'm not importing/using Tts anywhere. I'm on React-Native 44.2.

@tysoncadenhead
Copy link

I got this error too. Any update on why this would be happening?

@TaiWilkin
Copy link
Author

I uninstalled it, cleared my NPM cache, and reinstalled, then completely closed everything (simulator, my IDE, etc.) and restarted. Then it worked.

@tysoncadenhead
Copy link

That worked for me too. Thanks!

@Symous
Copy link

Symous commented Jul 25, 2017

Just run 'react-native run-ios/run-android' again and this error will disappear. :-)

@mrhandoko
Copy link

Not working

@ak1394 ak1394 closed this as completed Nov 8, 2017
@nicotroia
Copy link

This is still happening for me. Trying individual versions of this package and manually linking them but nothing is working. App always crashes at splash screen

@odeyatwi
Copy link

i did manual link:
https://facebook.github.io/react-native/docs/linking-libraries-ios#manual-linking

and if you get warning of "RCTBridge required dispatch_sync to load RCTDevLoadingView. This may lead to deadlocks" - place the libTextToSpeech.a file in the bottom of the linked libraries

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants