touch-packages team mailing list archive

[Kyle Nitzsche <kyle.nitzsche@xxxxxxxxxxxxx>]

It seems there are two issues here:

1) As noted, apparently ActionMetadata passed into PerformAction and
Activate methods is always Unknown

2) Network connectivity status should not be passed into the scope as an
enum because it can become stale and therefore can prevent a scope from
making good decisions based on *current* network status. Consider the
case where a user displays a Preview, puts the phone down, and comes
back an hour later, then clicks a Preview button. The code might want to
do different things if there is network and if there is not.

-- 
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