It is confusing for people in practice: many people want to check is_valid in cases where they shouldn't. I introduced it to avoid adding the ability to query the persistent error state to the IdentityManager API (for Sync's use case of detecting the refresh token being set to the invalid token). However, avoiding adding that API is no longer a priority. Let's get rid of this parameter altogether, replacing the one legitimate use case with querying GetPersistentErrorStateOfRefreshTokenForAccount().
Comment 1 by blundell@chromium.org
, Nov 27Status: Assigned (was: Available)