updates panel doesn't deal with invalid u1 tokens

[Thomas Strehl]

See attached screenshot: when having a system update available and some app updates then updating any app does not have any effect, meaning no download or installation starts for no apparent reason (there is also no feedback, the progress bar is shown but remains all the time at 0). The only thing that works on that page is installing the system update. If that is intentional it would be good to have some visual hints.

[Thomas Strehl (strehl-t)]

After updating the system, updating the pay ui is still not possible. It says downloading, but there is zero progress.

[Sebastien Bacher (seb128)]

Right, I can confirm that and it's not due to system updates

[Sebastien Bacher (seb128)]

the sso token were invalidated yesterday and apparently the stack has issues dealing with that, popey said that deleting and adding back the U1 account makes thing work

[Sebastien Bacher (seb128)]

Unassigning from Diego who is not working on settings anymore, need to find another owner there

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Matthew Paul Thomas (mpt)]

What does it mean to "deal with an invalid token"? Does every app that uses any online account have to cater for that case, or is it something that Online Accounts can/should do automatically?

[Seth Arnold (seth-arnold)]

mpt, there should be -some- kind of visual indication in the updates interface that an error has occurred and it should give the user some clues about why it failed. If there is an error message from the update server in the headers then that error should be passed along the users.

It currently just looks like we didn't implement updates.

[Jonathan Cave (jocave)]

Update from
   ubuntu-touch/stable/bq-aquaris.en r17 krillin
 to
   ubuntu-touch/stable/bq-aquaris.en r18 krillin

Previously configured U1 account disappeared during this OTA update. This device had a Google OA configured which was not removed.

[Jonathan Cave (jocave)]

The same behaviour present when upgrading from ubuntu-touch/stable/bq-aquaris.en r16 krillin

[David Barth (dbarth)]

Same for a U1 account created on r17. The upgrade to r18 had the account preserved. Which is technically that the ACLs protecting the account privacy have been upgraded in r17 and are considered up-to-date in upward releases.

[Pat McGowan (pat-mcgowan)]

tracking the ota deleting the u1 account and consider an early ota fix witht he solution from vivid

[Pat McGowan (pat-mcgowan)]

wrong bug

[dobey (dobey)]

@mpt It means dealing with an expired token. The network requests are all handled by the app, not online-accounts, so the apps have to deal with it individually. The correct way to handle this is to handle 401/403 errors by deleting the current token on the system, and opening the online-accounts UI for the account, to require logging in again.

@jocave, @dbarth: this is the wrong bug for that. The correct bug is #1413655

[Pat McGowan (pat-mcgowan)]

Can this get in the queue

[Launchpad Janitor (janitor)]

This bug was fixed in the package ubuntu-system-settings - 0.3+15.10.20150901-0ubuntu1

---------------
ubuntu-system-settings (0.3+15.10.20150901-0ubuntu1) wily; urgency=medium

  [ Ken VanDine ]
  * emit credentialsDeleted when the U1 token expired (LP: #1378678)

  [ Manuel de la Pena ]
  * Sign the query in order to get a possible auth error from the server
    and stop the user from trying to do updates with invalid creds.
  * The updates page is leaking objects when we have a successful update
    and when we do have errors. The following branch ensures that no
    memory is wasted.

 -- CI Train Bot <email address hidden> Tue, 01 Sep 2015 13:59:12 +0000