Chrome.identity.getAuthToken() throws exception only in a specific locale
Reported by
howo...@gmail.com,
Apr 11 2016
|
|||||||||||||||
Issue descriptionChrome Version : 49.0.2623.110 (64-bit) URLs (if applicable) : https://github.com/GoogleChrome/chrome-app-samples/issues/436 What steps will reproduce the problem? 1. Run the sample app and confirm that sign in works well. 2. Go to your language settings and change your language to Korean 3. Quit Chrome browser completely and open it again -- the browser should be in Korean now. 4. Run the sample app and encounter chrome.runtime.identity.getAuthToken: Authorization page could not be loaded error. What is the expected result? I should get the token in the callback without any exception in any locale What happens instead? You get an exception and token is undefined in the callback. This only happens in a specific locale. Please provide any additional information below. Attach a screenshot if possible. Problem: chrome.identity.getAuthToken() function throws {"message":"Authorization page could not be loaded."} error and returns undefined for token when a Chrome app runs in Korean locale. I was having this problem with my Chrome app (quite puzzling because sign in doesn't work only in a certain locale) and I thought I did something wrong. I came here to look for the answer, and found out that the sample app is having the same problem. I tried the following things: - Add the following domains to permissions in manifest.js "https://*.chromiumapp.org/*", "https://chromiumapp.org/", "https://*.apps.googleusercontent.com/", "https://apps.googleusercontent.com/", "https://apps.googleusercontent.com/", "https://*.chromiumapp.org/*/*", "*://*.google.com/*", "https://accounts.google.com/o/oauth2/v2/auth" - Add key field in manifest.js so that App ID is the same for both production and development. - Check that OAuth2 Client key has the right App ID. - Use chrome.identity.launchWebAuthFlow in place of chrome.identity.getAuthToken - Change the 'interactive': true option to false - Call chrome.identity.getAuthToken({ 'interactive': true } twice - Call chrome.identity.getAuthToken in the callback of chrome.identity.onSignInChanged None of the above worked. I am happy to invite you to see my code on GitHub if that helps.
,
Apr 13 2016
Thanks so much for working on this. I'd love to help in any way I can. This bug is affecting a production app, preventing Korean users from signing in.
,
Apr 13 2016
I found the same error when working on my extension. It seems that it's bug connected with browser language. If I'm using the English language then all works fine, but when I switched the browser to the Russian language, then this error occurred. My environment: Chrome version: 49.0.2623.112 m OS: Windows 10 Pro
,
Apr 16 2016
What's the status of this issue?
,
Apr 20 2016
,
May 10 2016
Hey, is there any action on this issue?
,
Jun 3 2016
bump
,
Jun 6 2016
Please Ani, can you have a look at this and triage accordingly?
,
Jun 6 2016
Adding Ben who might be able to better route this
,
Jun 7 2016
courage@ was the owner of this API, however he doesn't work on it any more :( Adding some other people who may be able to help. Albert - I assume this also affects ChromeOS, maybe know of engineers who could help out?
,
Jul 2 2016
Will anyone take a look at this? :)
,
Jul 11 2016
,
Aug 24 2016
,
Aug 24 2016
,
Mar 3 2017
,
Mar 3 2017
,
May 23 2017
Any progress on this? I've been struggling with this issue second day and get crazy
,
May 23 2017
,
May 23 2017
I think msarda@ and crew own the identity API nowadays.
,
May 24 2017
I've tried the Identity Sample app on ToT for coreean (by changing the language to coreen in chrome://chrome/settings/languages ) and everything is working fine for me. Do you have a similar issue for English, or is it only for other languages? If you're seeing it for English as well, then you may be hitting the Issue 722323 (I already have a patch for that here https://codereview.chromium.org/2901283002/ ).
,
May 24 2017
,
Jul 19 2017
I am seeing this scenario for a few users of my extension. For some calleing getAuthToken twice does the trick, for others, it always returns "Authorization page could not be loaded?" Any advice?
,
Jul 19 2017
I think this is a duplicate of Issue 722323 . Could you test it again on Chrome Canary as that patch should have landed now?
,
Oct 17
,
Oct 18
Closing this bug as I cannot repro it anymore. Please re-open if it still reproduces. |
|||||||||||||||
►
Sign in to add a comment |
|||||||||||||||
Comment 1 by fbeaufort@chromium.org
, Apr 12 2016Components: Platform>Apps
Status: Available (was: Unconfirmed)