-
-
Notifications
You must be signed in to change notification settings - Fork 276
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
Wrong port in connectivity check calls in 3.0.7 #422
Comments
Thanks for reporting this problem. It should be fixed soon. |
I tested it for port 443 and it didn't work in my case. I decided to change protocol from https into http in PR #425 because it works properly with default host. We can investigate this issue in the future in case of changing protocol back to https. I think not secure connection is not a big deal here because it's used just for "ping" - not for transmitting sensitive data. |
Describe the bug
After upgrading to 3.0.7
ReactiveNetwork.observeInternetConnectivity
stops working with:To Reproduce
Call
ReactiveNetwork.observeInternetConnectivity
.Expected behavior
true
is emitted on detected network connectivity.Smartphone (please complete the following information):
Additional context
3.0.6 works as expected with the default config and allowed cleartext.
The default config with 3.0.7 tries to reach
https://clients3.google.com/generate_204
on port80
.The following version with the manual port works as expected:
The text was updated successfully, but these errors were encountered: