Comment 8 for bug 1544033

The problem is that the way the U1 account is used, not only in the store scope, but in most everywhere it is used in the system, is that it is designed to work with or without an existing account in place, and we only explicitly require an account when one is absolutely required for some function, and only via some specific user interaction, rather than simply background requests to see if an account exists.

The proposed solution not only requires small changes, but a general complete re-design of how the account is used across the entire system. This is not a simple thing to do, and the changes would be very disruptive to the flows we have in place.