Bugzilla – Bug 11871
SBS does not prompt the user when SN account has changed
Last modified: 2019-01-25 12:04:21 UTC
SC does not tell the user that there is a problem logging onto the registered SN account. If I change the password via SN, SC will not pick up the new password and or prompt the user to change the password. This will lead to bug 11868 SC should check and prompt the user when ever it can not validate the associated SN account.
Andy needs to know when to show this error. The goal from the QA perspective is that the user needs an error message that indicates to them how to fix the problem. We can't just let support puzzle it out from the fact that no SN services work any more.
Can I get a little more clarification on when this case gets triggered? Is it triggered by user action (when the user navigates into a music service, navigating into home menu, etc) or could this happen while the device is essentially "idle?" Knowing the case makes it much easier to provide a solution. It sounds like this needs to be a standard-looking error screen with some sort of "your account settings have changed" etc. with the opportunity to either switch accounts or re-enter the password...
Scenario 1: Running SC, valid SN credentials, user connects devices to SN. User changes Password via SN.com then moves devices back to SC. Attempting to navigate to any service will be affected. Scenario 2: Running SC, valid SN credentials, devices attached to SC and IDLE. User changes Password via SN.com. Attempting to play any service will be affected. Scenario 3: Running SC, valid SN credentials, devices attached to SC and Streaming. User changes Password via SN.com. Attempting to play any NEW stream will be affected. Scenario 4: Stopped SC, with valid SN credentials, devices attached to SC. User changes Password via SN.com. Starting SC and attempting to play any service will be affected.
this is an administrative shuffle on priority fields to help make better judgment on the top end of the priority list. P4->P5, P3->P4, and P2->P3.
This is actually kind of a serious issue, reprioritizing to P1
Matt Weldon doesn't work for us any more.
Unassigned bugs cannot have a priority.