Affects Version/s: 1.3.0
Fix Version/s: None
Samsung Galaxy Edge S6 / Android 6
useragent: "Mozilla/5.0 (Linux; Android 6.0.1; SM-G925F Build/MMB29K; wv) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Chrome/53.0.2785.124 Mobile Safari/537.36"
firstname.lastname@example.orgSamsung Galaxy Edge S6 / Android 6 useragent: "Mozilla/5.0 (Linux; Android 6.0.1; SM-G925F Build/MMB29K; wv) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Chrome/53.0.2785.124 Mobile Safari/537.36" reproduced with: email@example.com (latest) firstname.lastname@example.org
I've noticed that information exposed by the plugin is not reliable. It happens often that I'm connected to the internet via WiFi, and the plugin says that there's no connection.
It's not easy to reproduce it on-demand, but I reproduced it many times recently. It happens most often when in the morning, I open the Cordova app that was running in background throughout the night.
Then, when I connect to Chrome Dev Tools, I can do a repl session like this:
So, the plugin thinks I'm offline, yet any HTTP calls done within the app without checking if I'm offline or online, are successful (either from the app or devtools).
When I disable WiFi and reenable it, after a few seconds the plugin updates its state and then it tells that connection type is "wifi".
There are several possibilities here:
- either system (or device driver) gives us incorrect information, or
- cordova plugin is caching data and/or not listening properly to all the events and/or incorrectly processing it
and most probably the issue manifests itself when the device is asleep for many hours (but I'm not sure about this).
Note that I also noticed another issue, that sometimes the Chrome network stack thinks I'm offline (when I do an HTTP call, it fails immediately and I see network errors in devtools console) - and then I restart the Cordova app, and everything's fine, all HTTP calls are ok - but this is unrelated to this ticket, and perhaps a bug in Chrome.
This ticket seems to be most likely a bug in the plugin, because as I said before, doing HTTP call succeeds despite the plugin telling me that I'm offline.