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.

Sign up for GitHub

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

Jump to bottom

Argument 0 (NSNumber) of RCTWebViewManager.bridgeSetup must not be null #39

Closed
CorpusCallosum opened this issue Nov 25, 2015 · 2 comments
Closed

Argument 0 (NSNumber) of RCTWebViewManager.bridgeSetup must not be null #39

CorpusCallosum opened this issue Nov 25, 2015 · 2 comments

Comments

@CorpusCallosum
Copy link
Contributor

I'm getting this error:

Argument 0 (NSNumber) of RCTWebViewManager.bridgeSetup must not be null

What does it mean?

Thanks,
Jack
@nycoliver
Copy link

I'm getting a very similar error:

Argument 0 (NSNumber) of RCTWebViewManager.onMessage must not be null

It happens when I rerender the component containing the webview as another component without a webview. Don't think I am doing anything wrong...

@alinz
Copy link
Owner

alinz commented Dec 9, 2015

@CorpusCallosum and @Ikeafurniture I don't think this issue will happen with the new release. Please try the new release. Make sure that you guys are using the react-native 0.16 and above. Please reopen this issue if you have the same error

@alinz alinz closed this as completed Dec 9, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@CorpusCallosum @alinz @nycoliver