UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.81 Safari/537.36

Steps to reproduce the problem:
1. Create a new instance of Chrome with a new user dir, e.g.
open -a "Google Chrome" --args --user-data-dir=/Users/user/chrometestdir --extensions-update-frequency=30
2. Once the instance has started, kill the instance
3. Start a new instance of Chrome with the same user dir as created in step (1)
4. Now sign into Google Chrome with a "Managed Account"
5. When the "Link my Chrome data to this account" dialog pops up, click on the "Create a new profile" option
6. Visit chrome://extensions and load the attached extension
7. Launch the "Identity API Sample" and click on the "Sign In" button
8. "Allow" the permissions in the popup which appears
9. Kill the Chrome instance again
10. Start a new instance of Chrome with the same user dir as created in step (1)
11. Launch the "Identity API Sample" again
12. Click on "Sign In"

What is the expected behavior?
The OAuth popup should know that the user has previously allowed access to the specified scopes and not appear after the first acceptance.

What went wrong?
The user has already accepted all scopes in the manifest.json - the OAuth popup should know that the user has allowed access and not appear after the first acceptance. Repeating steps 9-12 will cause the OAuth popup to repeatedly appear.

Did this work before? N/A 

Does this work in other browsers? N/A

Chrome version: 58.0.3029.81  Channel: stable
OS Version: OS X 10.12.4
Flash Version: 

This issue only occurs with the following OAuth scopes:
https://www.googleapis.com/auth/documents
https://www.googleapis.com/auth/spreadsheets

When using the following Chrome Identity API call:
chrome.identity.getAuthToken({ 'interactive': true }, function(token) {
});
 

Deleted: identity-sample.zip 367 KB

identity-sample.zip 367 KB Download