-
Notifications
You must be signed in to change notification settings - Fork 5k
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
React native url == null (WebsocketProvider) #2864
Comments
Could you create a GitHub repository with an example project where this error happens? Otherwise, it will be hard to reproduce this issue 1:1. |
@nivida here repo. I took the main project and delete unnecessary parts, I apologize for the unnecessary dependences =( For reproduce: Run app, then push button, in logs you seee some events. The easiest way to reproduce is to connect the phone by USB, running the build and then turn off Wi-Fi or cellular network. You need wait some timeout, about 10 sec. |
bug in react native |
@sirpy Thanks for proposing this PR in the |
Summary: Conform with Websocket javascript api. related to web3js issues: web3/web3.js#2864 web3/web3.js#2602 Reviewed By: javache Differential Revision: D25927475 Pulled By: TheSavior fbshipit-source-id: 26b2df0565dac581d546b6824dd4f0fc2c8cdc32
Description
Hi) While writing an application on RN, there were problems with catching exceptions during internet connection loss. If I have already call
new Web3.providers.WebsocketProvider(urlConfig);
then when the connection is lost, the application crashes without causing try/catch.Expected behavior
Calling
new Web3.providers.WebsocketProvider(urlConfig);
when connection lost must throw some exception.Actual behavior
Just crash without logs in logger, but with screen logs.
Error Logs
Versions
Thank you!
The text was updated successfully, but these errors were encountered: