New issue
Advanced search Search tips

Issue 749038 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Feb 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug



Sign in to add a comment

[Dice] Fix auth errors based on SigninErrorController instead of Sync

Project Member Reported by droger@chromium.org, Jul 26 2017

Issue description

Dice is fixing auth error when the Sync service is in auth error state.

The related code was introduced in CL:
https://chromium-review.googlesource.com/c/584527

However, a sync service error does not match exactly the error UI.

Typically, after revoking a token, the sync service detects the authentication error after a delay (a couple hours maybe, and even a Chrome restart does not necesssarily put Sync in error state), whereas the SigninErrorController (and the UI in Chrome) shows the error UI earlier than that (almost instantly, and definitely on Chrome restart).

It would by slightly better to use the same signal as the UI in Dice:
- more consistent with the UI
- easier to test (having a delay of a couple hours makes the feature harder to test)
- fixing errors earlier is generally a good thing


This is filed as a blocking bug for the feature, but it is probably actually optional.
 
Project Member

Comment 1 by sheriffbot@chromium.org, Aug 25 2017

Status: Available (was: Assigned)
--Chrome Identity automated triaging--

This bug is Assigned and has gone one month without any activity, so it is being moved to Available to indicate that it is not actively being worked on. If you are working on this bug, please mark yourself as the owner and move back to Assigned. Please see https://goo.gl/78kbny for more details. Please remove the Services>SignIn or UI>Browser>Profiles components if this bug isn't related to Chrome Identity.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 2 by msarda@chromium.org, Aug 28 2017

Status: Assigned (was: Available)
Keeping this assigned as this is still relevant.

Comment 3 by ew...@chromium.org, Sep 6 2017

Blocking: -743110
Cc: ew...@chromium.org
Labels: -Pri-3 Pri-2
Just noticed this. I don't think it's blocking (so I'm going to remove the blocking bug), but definitely seems like a nice-to-have improvement.
Project Member

Comment 4 by sheriffbot@chromium.org, Oct 9 2017

Status: Available (was: Assigned)
--Chrome Identity automated triaging--

This bug is Assigned and has gone one month without any activity, so it is being moved to Available to indicate that it is not actively being worked on. If you are working on this bug, please mark yourself as the owner and move back to Assigned. Please see https://goo.gl/78kbny for more details. Please remove the Services>SignIn or UI>Browser>Profiles components if this bug isn't related to Chrome Identity.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 5 by ew...@chromium.org, Oct 9 2017

Status: Assigned (was: Available)
Project Member

Comment 6 by sheriffbot@chromium.org, Nov 9 2017

Status: Available (was: Assigned)
--Chrome Identity automated triaging--

This bug is Assigned and has gone one month without any activity, so it is being moved to Available to indicate that it is not actively being worked on. If you are working on this bug, please mark yourself as the owner and move back to Assigned. Please see https://goo.gl/78kbny for more details. Please remove the Services>SignIn or UI>Browser>Profiles components if this bug isn't related to Chrome Identity.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 7 by droger@chromium.org, Feb 13 2018

Status: WontFix (was: Available)
Not worth doing at this point, DiceFixAuthErrors will be superseded by Dice soon.

Sign in to add a comment