touch-packages team mailing list archive

[Michi Henning <michi.henning@xxxxxxxxxxxxx>]

You are always free to ignore the network status. It was moved in mainly
as a convenience feature, to allow a scope to immediately notice if, for
example, the device is in flight mode. Given the problems with
NetworkAccessManager (still not completely resolved), I would probably
interpret "unknown" to mean "available" and go ahead, and only pay
attention if the status indicates "network down".

The issue with ActionMetadata and PerformAction not receiving the
network status needs looking at.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-scopes-shell in
Ubuntu.
https://bugs.launchpad.net/bugs/1502282

Title:
  "unknown" connectivity status problematic

Status in The Savilerow project:
  New
Status in unity-scopes-api package in Ubuntu:
  Confirmed
Status in unity-scopes-shell package in Ubuntu:
  Confirmed

Bug description:
  metadata provides a scope a network connectivity status enum with three possible states:
  * connected
  * disconnected
  * unknown

  Sometimes unknown is the current state. This is quite problematic
  because in general a scopes that queries the network (that is, most
  scopes) need to know whether there is network or is not network and
  depending on this either make the network queries or display an error
  message.

  A status of unknown connectivity leaves the scope with no valid option:
  * the scope could assume the network is down and provide the user an error message. But often the network is not actually down, so this interrupts the user's flow unnecessarily
  *  the scope could assume the network is up, but this is dangerous if it is not up

To manage notifications about this bug go to:
https://bugs.launchpad.net/savilerow/+bug/1502282/+subscriptions