New issue
Advanced search Search tips

Issue 597550 link

Starred by 3 users

Issue metadata

Status: Duplicate
Merged: issue 656418
Owner:
Closed: Jun 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 3
Type: Bug



Sign in to add a comment

Chromium (ChromePublic.apk) can't access Google accounts on M or later

Project Member Reported by bauerb@chromium.org, Mar 24 2016

Issue description

Since Android M, listing Google accounts requires the Contacts permission (which is a runtime permission, so it's not automatically granted).

For Chrome, we can use a first-party Google Play Services API to list Google accounts, but that's not available for ChromePublic, and there is no code that would ask the user for that permission, so we return an empty list of accounts, which means the UI tells the user that there are no Google accounts present. This is confusing to developers.
 
Project Member

Comment 1 by sheriffbot@chromium.org, Mar 23 2017

Cc: ew...@chromium.org jlebel@chromium.org bsazonov@chromium.org msarda@chromium.org
--Chrome Identity automated triaging--

This bug is Available and has gone one year without any activity. If another month passes without any activity, this bug will be closed out. Please provide an update with the latest status for this bug. Please see https://goo.gl/78kbny for more details. Please remove the Services>SignIn or UI>Browser>Profiles components if this bug isn't related to Chrome Identity.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Owner: bsazonov@chromium.org

Comment 3 by ew...@chromium.org, Mar 23 2017

Just FYI, I view this as quite low-priority Boris. It's really a convenience thing for developers.

I think we can just pop up some dialogue asking for contacts permission at the moment when we first need to list the accounts (e.g. before showing the sign-in screen).
Mergedinto: 656418
Status: Duplicate (was: Available)

Sign in to add a comment