Issue metadata
Sign in to add a comment
|
Sign in to chromium on android not working
Reported by
johnygma...@gmail.com,
Feb 2 2017
|
||||||||||||||||||||||||
Issue descriptionSteps 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.
,
Feb 2 2017
,
Feb 2 2017
Thanks for the report! Can you provide below info for further triage? 1. Chrome version 2. Device details
,
Feb 2 2017
1. Chromium for android version 58.0.3001.0 2. Device Nexus 6p
,
Feb 2 2017
,
Feb 2 2017
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
,
Feb 2 2017
Ok. Can you provide chrome://signin-internals page ?
,
Feb 2 2017
Is this enough ? I have attached. I am trying to sync between to Chromium on Linux and Chromium on Android.
,
Feb 2 2017
,
Feb 2 2017
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 |
|||||||||||||||||||||||||
Comment 1 by s...@chromium.org
, Feb 2 2017