-
Notifications
You must be signed in to change notification settings - Fork 272
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
checkInternetConnection only works once #115
Comments
@reilem did you find a solution? I am finding when I go offline, my queue fills up (adding |
I ended up writing my own internet connection check by just sending a HEAD to our backend.
You could then use the |
Experiencing the same problem. Maybe the platform specific check is not working:
|
@BoostIO funded this issue with $10. Visit this issue on Issuehunt |
Looking into the native code for iOS, I don't see anything that suggests that Reference here https://github.com/facebook/react-native/blob/master/React/Modules/RCTEventEmitter.m
Something close to this should do the trick...
|
@issuehuntfest has funded $90.00 to this issue. See it on IssueHunt |
@fabiancook has submitted a pull request. See it on IssueHunt |
@rgommezz has cancelled their pull request. See it on IssueHunt |
@rgommezz has submitted a pull request. See it on IssueHunt |
This is an issue I'm having (at least on iOS). The method checkInternetConnection() works perfectly fine the first time around and returns correct results. However when I call it a second time it seems to hang at this bit:
The second time around "TEST 1" is printed but "TEST 2" is not. I'm thinking that maybe the listeners are not being cleared properly which is causing the promise to not be resolved the second time around. Consequently
checkInternetAccess()
is never entered the second time around either and so the whole thing just hangs whenever I try toawait checkInternetConnection()
.I'll probably try implementing this one myself as its quite tricky to get working. I'll report back if I find a working solution.
The text was updated successfully, but these errors were encountered: