Can't sync google account data on Chromium for android app
Reported by
hengyi.n...@gmail.com,
Dec 25
|
|||||
Issue description
Steps to reproduce the problem:
1. I already apply api key and client ID on Google Cloud platform (type is android)
2. then I build chromium for android with google_api_key and client id
3. I run this apk and sign in google account. There can't sync data (I install google service already)
What is the expected behavior?
It can sync google account data.
What went wrong?
It still show setup in progress.
And report below error.
018-12-25 14:17:29.370 2389-3957/? W/ActivityManager: Failed setting process group of 21024 to 0
2018-12-25 14:17:29.438 20494-20545/? W/Auth: [GoogleAuthUtil] GoogleAuthUtil
2018-12-25 14:17:29.444 20494-20545/? W/GoogleAuthUtil: Error when getting token
com.google.android.gms.auth.UserRecoverableAuthException: NeedPermission
at com.google.android.gms.auth.zze$1.zzat(Unknown Source)
at com.google.android.gms.auth.zze$1.zzau(Unknown Source)
at com.google.android.gms.auth.zze.zza(Unknown Source)
at com.google.android.gms.auth.zze.zzc(Unknown Source)
at com.google.android.gms.auth.GoogleAuthUtil.zzc(Unknown Source)
at com.google.android.gms.auth.GoogleAuthUtil.zzb(Unknown Source)
at com.google.android.gms.auth.GoogleAuthUtil.zza(Unknown Source)
at com.google.android.gms.auth.GoogleAuthUtil.getTokenWithNotification(Unknown Source)
at org.chromium.components.signin.SystemAccountManagerDelegate.getAuthToken(SystemAccountManagerDelegate.java:70)
at org.chromium.components.signin.AccountManagerHelper$6.run(AccountManagerHelper.java:304)
at org.chromium.components.signin.AccountManagerHelper$6.run(AccountManagerHelper.java:301)
at org.chromium.components.signin.AccountManagerHelper$ConnectionRetry$1.doInBackground(AccountManagerHelper.java:423)
at org.chromium.components.signin.AccountManagerHelper$ConnectionRetry$1.doInBackground(AccountManagerHelper.java:419)
at android.os.AsyncTask$2.call(AsyncTask.java:304)
at java.util.concurrent.FutureTask.run(FutureTask.java:237)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1133)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:607)
at java.lang.Thread.run(Thread.java:761)
2018-12-25 14:17:29.446 20494-20545/? W/cr_Sync_Signin: Failed to perform auth task
org.chromium.components.signin.AuthException: com.google.android.gms.auth.UserRecoverableNotifiedException: User intervention required. Notification has been pushed.
at org.chromium.components.signin.SystemAccountManagerDelegate.getAuthToken(SystemAccountManagerDelegate.java:76)
at org.chromium.components.signin.AccountManagerHelper$6.run(AccountManagerHelper.java:304)
at org.chromium.components.signin.AccountManagerHelper$6.run(AccountManagerHelper.java:301)
at org.chromium.components.signin.AccountManagerHelper$ConnectionRetry$1.doInBackground(AccountManagerHelper.java:423)
at org.chromium.components.signin.AccountManagerHelper$ConnectionRetry$1.doInBackground(AccountManagerHelper.java:419)
at android.os.AsyncTask$2.call(AsyncTask.java:304)
at java.util.concurrent.FutureTask.run(FutureTask.java:237)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1133)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:607)
at java.lang.Thread.run(Thread.java:761)
Caused by: com.google.android.gms.auth.UserRecoverableNotifiedException: User intervention required. Notification has been pushed.
at com.google.android.gms.auth.GoogleAuthUtil.zzb(Unknown Source)
at com.google.android.gms.auth.GoogleAuthUtil.zza(Unknown Source)
at com.google.android.gms.auth.GoogleAuthUtil.getTokenWithNotification(Unknown Source)
at org.chromium.components.signin.SystemAccountManagerDelegate.getAuthToken(SystemAccountManagerDelegate.java:70)
at org.chromium.components.signin.AccountManagerHelper$6.run(AccountManagerHelper.java:304)
at org.chromium.components.signin.AccountManagerHelper$6.run(AccountManagerHelper.java:301)
at org.chromium.components.signin.AccountManagerHelper$ConnectionRetry$1.doInBackground(AccountManagerHelper.java:423)
at org.chromium.components.signin.AccountManagerHelper$ConnectionRetry$1.doInBackground(AccountManagerHelper.java:419)
at android.os.AsyncTask$2.call(AsyncTask.java:304)
at java.util.concurrent.FutureTask.run(FutureTask.java:237)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1133)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:607)
at java.lang.Thread.run(Thread.java:761)
Did this work before? No
Does this work in other browsers? N/A
Chrome version: 60.0.3112.20 Channel: stable
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version: 7.0
,
Dec 26
@ hengyi.ning: Seems like you are using very older version of Chrome, could you please let us know of this is still happening with latest chrome #71.0.3578.99. Thanks!
,
Dec 27
chelamcherla@chromium.org Thanks for your help, chelamcherla. It's still happening with #73.0.3625.0 1. I already enabled Chrome Sync API at Google Cloud platform.but there is still report below exception for https://www.googleapis.com/auth/chromesync and https://www.googleapis.com/accounts/OAuthLogin scope. Failed to perform auth task org.chromium.components.signin.AuthException: com.google.android.gms.auth.GoogleAuthException: INVALID_SCOPE at org.chromium.components.signin.SystemAccountManagerDelegate.getAuthToken(SystemAccountManagerDelegate.java:76) at org.chromium.components.signin.AccountManagerHelper$6.run(AccountManagerHelper.java:304) at org.chromium.components.signin.AccountManagerHelper$6.run(AccountManagerHelper.java:301) at org.chromium.components.signin.AccountManagerHelper$ConnectionRetry$1.doInBackground(AccountManagerHelper.java:423) at org.chromium.components.signin.AccountManagerHelper$ConnectionRetry$1.doInBackground(AccountManagerHelper.java:419) at android.os.AsyncTask$2.call(AsyncTask.java:305) at java.util.concurrent.FutureTask.run(FutureTask.java:237) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1133) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:607) at java.lang.Thread.run(Thread.java:761) Caused by: com.google.android.gms.auth.GoogleAuthException: INVALID_SCOPE at com.google.android.gms.auth.zze$1.zzat(Unknown Source) at com.google.android.gms.auth.zze$1.zzau(Unknown Source) at com.google.android.gms.auth.zze.zza(Unknown Source) at com.google.android.gms.auth.zze.zzc(Unknown Source) at com.google.android.gms.auth.GoogleAuthUtil.zzc(Unknown Source) at com.google.android.gms.auth.GoogleAuthUtil.zzb(Unknown Source) at com.google.android.gms.auth.GoogleAuthUtil.zza(Unknown Source) at com.google.android.gms.auth.GoogleAuthUtil.getTokenWithNotification(Unknown Source) at org.chromium.components.signin.SystemAccountManagerDelegate.getAuthToken(SystemAccountManagerDelegate.java:70) at org.chromium.components.signin.AccountManagerHelper$6.run(AccountManagerHelper.java:304) at org.chromium.components.signin.AccountManagerHelper$6.run(AccountManagerHelper.java:301) at org.chromium.components.signin.AccountManagerHelper$ConnectionRetry$1.doInBackground(AccountManagerHelper.java:423) at org.chromium.components.signin.AccountManagerHelper$ConnectionRetry$1.doInBackground(AccountManagerHelper.java:419) at android.os.AsyncTask$2.call(AsyncTask.java:305) at java.util.concurrent.FutureTask.run(FutureTask.java:237) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1133) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:607) at java.lang.Thread.run(Thread.java:761) Is there something I need to config or lost something? Thanks a lot. I look forward your reply.
,
Dec 27
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Dec 27
hi sheriffbot, Is it support sync google account data by Chromium for android? I use credential on Chromium for window, It works. But I add credential(api key and OAuth client) which is android type , it can't sync data. This almost confused me . So, is it support? Thank for your help. I build chromium for android by myself and build. args.gn file contains below:
,
Dec 28
Is it like this article, google does not support chrome sync, including chromium for android. https://www.ghacks.net/2017/01/25/google-shuts-down-chrome-sync-for-third-party-browsers-on-android/ https://www.androidpolice.com/2017/01/24/google-shuts-off-chrome-sync-api-third-party-browsers-android-citing-security-vulnerability/ This article was published on January 25, 2017.Is Google now starting to support it?
,
Dec 28
Issue 917990 has been merged into this issue.
,
Dec 28
Issue 917947 has been merged into this issue.
,
Dec 28
Could someone from Services>Sync team please confirm the issue, this seems to be wont-fix. Thanks!
,
Jan 7
Assigning to treib@ who knows best about it.
,
Jan 7
Looking at https://www.chromium.org/developers/how-tos/api-keys, it seems you failed to provide the OAuth client secret? Either way, this is about some configuration issue with a manually-built chromium apk; it's not a bug in Chrome. For future questions like this, please do not file bugs. You can try contacting chromium-dev@chromium.org instead, *after* reading the instructions at https://www.chromium.org/developers and searching for existing email threads on the problem.
,
Jan 9
@ treib@chromium.org Thanks for your help. But I already required the OAuth client secret like picture which I uploaded. And I add it to args.gn to build chromium apk like picture which I uploaded. I was confused why it's invalid. Can you give me more information? Thanks.
,
Jan 9
@ treib@chromium.org By the way, I apply the client ID for Android. It haven't provide client secret? Only apply Client ID for other type have client secret , maybe i need to apply Client Id for other type? Even though I already try it(It failed too)
,
Jan 9
In your args.gn picture, there is a client *ID* but not a client *secret*. That is probably why signing in doesn't work. Please read the instructions at https://www.chromium.org/developers/how-tos/api-keys carefully and notice this line: google_default_client_secret = "your_client_secret" If there is no client secret, you've probably selected the wrong type of credential. Again, *carefully* read https://www.chromium.org/developers/how-tos/api-keys.
,
Jan 11
Issue 920707 has been merged into this issue.
,
Jan 15
Sincerely, thanks for your help. 1. I selected *Android* type of credential for chromium for android, is it right? If not, which type is right? I'm not sure about this. If right, I'm sure there is no client secret for android. Please help me to check. 2.And Why I already enable Google Sync API, it still not shown in picture which named "apilist". Sync google account need to enable sync api, right? 3. I already readed https://www.chromium.org/developers/how-tos/api-keys many times. it's only mentioned *other* type of credential, not mentioned *android* type. So I'm confused. If the right type of credential is Other, I already try it. It can't sync data either.
,
Jan 15
,
Jan 15
I have no information on this beyond the documentation I pointed you to. If that says to use "Other", then that's probably what you should do.
,
Jan 16
I was used "Other", it works for chromium for window, not works for Android. o(╥﹏╥)o. Who can help me? Maybe this article is right. Google only support google account sync for Chrome, not chromium for Android. https://www.ghacks.net/2017/01/25/google-shuts-down-chrome-sync-for-third-party-browsers-on-android/ https://www.androidpolice.com/2017/01/24/google-shuts-off-chrome-sync-api-third-party-browsers-android-citing-security-vulnerability/ |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by chelamcherla@chromium.org
, Dec 26