There are a few issues with the 'new user' notification logic that will cause it to be on screen when it shouldn't be. I'm not 100% confident in this, but my understanding of the treatment of notifications that come in during OOBE is that appear in the background as soon as they are triggered so the user can't see them until OOBE is finished, but for purposes of handling them in our logic, they're already on screen. If I'm off in that understanding, the solutions below are probably going to require revision.
ISSUES
(1) User completes setup flow on Chromebook A, logs into Chromebook B for the first time, and then forgets their phone on Chromebook B. See crbug.com/881142#c11 for more detail.
(2) If the user completes setup in OOBE, the notification will be visible when they finish. Note: at the moment this would most likely be replaced by the 'Chromebook added' (which is also undesirable behavior) but once crbug.com/884373 is complete, the 'new user' notification will be there instead.
(3) If the notification comes up on Chromebook A and the user sets a host on Chromebook B, while waiting for verification the 'new user' notification will still be visible on A.
(4) If the user skips setup in OOBE, the 'new user' notification will be visible when they finish, (which is spammy since they just refused). Note: this is listed separately from (2) because its solution is different.
-----
SOLUTIONS
(1) Never show the 'new user' notification on Chromebook B if the user has seen any of the MultiDevice notifications on Chromebook B before because, if they're in this position, they should have seen the 'Chromebook added' notification when they first logged onto Chromebook B.
(2) & (3) Whenever there is a host status change, if the new host status is not 'potential hosts exist' (i.e. there are eligible hosts but none have been set), we remove the 'new user' notification if it's present.
(4) When the user presses the skip button in OOBE, we remove the 'new user' notification if present.
Comment 1 by jhawkins@chromium.org
, Oct 8