New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 688028 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 677887
Owner: ----
Closed: Feb 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: Bug



Sign in to add a comment

Sign in to chromium on android not working

Reported by johnygma...@gmail.com, Feb 2 2017

Issue description

Steps to reproduce the problem:
1. Sign In to Chromium on Android
2. Enter credentials
3. 

What is the expected behavior?
Chromium syncing with my login at pc.

What went wrong?
An error message comes with the following message. `The account already exists on your device.`

Did this work before? N/A 

Chrome version: version Developer Build  Channel: stable
OS Version: 7.1.1
Flash Version: 

I tried to delete my google account from the phone and redo all the steps. Still it didn't work. I am not able to sign in to the sync functionality in chromium.

 

Comment 1 by s...@chromium.org, Feb 2 2017

Components: Services Services>SignIn

Comment 2 by s...@chromium.org, Feb 2 2017

Components: -Services
Labels: Needs-Feedback
Thanks for the report! Can you provide below info for further triage?

1. Chrome version
2. Device details
1. Chromium for android version 58.0.3001.0
2. Device Nexus 6p
Mergedinto: 677887
Status: Duplicate (was: Unconfirmed)
I can't see the that corresponding bug.

You do not have permission to view the requested page. 

Reason: User is not allowed to view this issue

Ok. Can you provide chrome://signin-internals page ?
Is this enough ? I have attached. I am trying to sync between to Chromium on Linux and Chromium on Android.
Screenshot from 2017-02-02 19-23-03.png
159 KB View Download
Cc: maxbogue@chromium.org zea@chromium.org ew...@chromium.org bzanotti@chromium.org
I removed the view restrictions on the other bug, so you can see the discussion there.

Copying the relevant comment here:

We locked down access to chromesync scoped refresh tokens to address a security vulnerability. When we did so, we knew that this may break some 3P browsers on Android which made use of chromesync scoped refresh tokens to leverage Chrome Sync for their users.

Chrome Sync has never officially been supported for 3P browsers. We do not intend to create a solution by which 3P browsers can whitelist themselves or their users so that they can get chromesync scoped refresh tokens. Note that Chromium for Android is technically considered a 3P browser.

Marking as WontFix, accordingly.

Sign in to add a comment