-
Notifications
You must be signed in to change notification settings - Fork 47
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
Bad Address Causes Repeated Failure #27
Comments
RoJoHub
added a commit
that referenced
this issue
Mar 29, 2019
1. add timeout 2. add Error code 3. fix #27
RoJoHub
added a commit
that referenced
this issue
Mar 29, 2019
1. add timeout 2. add Error code 3. fix #27
RoJoHub
added a commit
that referenced
this issue
Mar 29, 2019
1. add timeout 2. add Error code 3. fix #27
RoJoHub
added a commit
that referenced
this issue
Mar 29, 2019
1. add timeout 2. add Error code 3. fix #27
RoJoHub
added a commit
that referenced
this issue
Mar 29, 2019
1. add timeout 2. add Error code 3. fix #27
Please update to |
Works perfectly. Thanks so much for your help!!
/Alan
…________________________________
From: Jerry.Luo <notifications@github.com>
Sent: Friday, March 29, 2019 1:35 AM
To: RoJoHub/react-native-ping
Cc: ajones2k; Author
Subject: Re: [RoJoHub/react-native-ping] Bad Address Causes Repeated Failure (#27)
Please update to 1.2.0.
This problem has been fixed in version 1.2.0.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<#27 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AX3F5xEqjleuySv1ksYbocsGxzU3SOd8ks5vbaYtgaJpZM4cQFWM>.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If I ping a good address
ms = await Ping.start('8.8.8.8'); //works
then a bad address
ms = await Ping.start('8.8.8.9'); //fails
then trying to ping the good address again always fails unless I restart the app
ms = await Ping.start('8.8.8.8'); //fails
Is there anyway to 'reset' the library to prevent this problem.
The text was updated successfully, but these errors were encountered: