On ChromeOS, IdentityManager has its primary account info set by UserSessionManager (see crbug.com/814787). At this point in the flow, the email address that UserSessionManager knows about is the sanitized email address. Hence, that is what gets set with IdentityManager. However, this email address can be updated in AccountTrackerService later on in response to the user info being fetched (see details in crbug.com/842041); in particular, if the user entered a non-sanitized version when creating their gmail account (e.g., f.o.o@gmail.com vs. foo@gmail.com), it will get updated to the user-entered version. I'm inserting a hack so that IdentityManager updates its email address in these cases. However, we should determine the long-term solution for this problem.