Comment 27 for bug 1637841

Revision history for this message
Michi Henning (michihenning) wrote :

The connectivity status is something that is *not* set by scopes-api. Instead, the status is received by scopes-api from whoever makes the query (typically, the shell) and then passed through to the scope. In turn, the shell just passes on what it gets from QNetworkAccessManager, I believe.

We had bugs open against QNAM for this and there were some changes made, but it's still flaky.

At any rate, the connectivity status is unlikely to be useful in debugging this issue because scopes-api never pays attention to it.