Bumping to P1. 

Your first run of Chrome should not include an error state. Especially not an error state that asks you to "re-enable" things you never installed/enabled. 

One other detail about my setup: I had also installed 51 stable before installing canary.

+mamir.  I wouldn't be surprised if this is a result of removing the creation flags from pending extension info, since that would then mean that bundled extensions never got the "installed by default" flag.

Likely happening on M53 already, so this will require a merge once fixed and landed on trunk. Please mark this bug as "Merge-Requested" once you confirmed the change to work on trunk.

M53 beta launch is coming soon.Your bug is labelled as Beta ReleaseBlock, pls make sure to land the fix before 6:00 PM PST, Monday (07/18/16). Thank you.

It has my full attention and it's currently my top priority.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/0128d5a9b0a402cd85aa0ef409c73f3ad1df548c

commit 0128d5a9b0a402cd85aa0ef409c73f3ad1df548c
Author: mamir <mamir@chromium.org>
Date: Fri Jul 15 20:55:48 2016

Adding the creation_flags back to pending_extension_info.
Add a unit test to cover the case when an external extension
is updated before being installed and make sure it retains
the creation flags.

BUG= 627522 

Review-Url: https://codereview.chromium.org/2146963004
Cr-Commit-Position: refs/heads/master@{#405856}

[modify] https://crrev.com/0128d5a9b0a402cd85aa0ef409c73f3ad1df548c/chrome/browser/extensions/extension_service.cc
[modify] https://crrev.com/0128d5a9b0a402cd85aa0ef409c73f3ad1df548c/chrome/browser/extensions/extension_service_unittest.cc
[modify] https://crrev.com/0128d5a9b0a402cd85aa0ef409c73f3ad1df548c/chrome/browser/extensions/pending_extension_info.cc
[modify] https://crrev.com/0128d5a9b0a402cd85aa0ef409c73f3ad1df548c/chrome/browser/extensions/pending_extension_info.h
[modify] https://crrev.com/0128d5a9b0a402cd85aa0ef409c73f3ad1df548c/chrome/browser/extensions/pending_extension_manager.cc
[modify] https://crrev.com/0128d5a9b0a402cd85aa0ef409c73f3ad1df548c/chrome/browser/extensions/pending_extension_manager.h
[modify] https://crrev.com/0128d5a9b0a402cd85aa0ef409c73f3ad1df548c/chrome/browser/extensions/updater/extension_updater_unittest.cc

Fix has landed. (together with a unit test for this edgy case)

I will not have access to a Win 10 machine over the weekend.
However, I will try to test on Mac upon the next Canary release.

Once we have some coverage on Canary over the weekend and it's safe can you please request for to merge to M53(2785) branch.

I tested Canary version 54.0.2799.0 on Mac 10.11.5, and the issue is fixed there.
No permissions prompt are shown upon the first run.

Your change meets the bar and is auto-approved for M53 (branch: 2785)

Please merge your change to M53 branch 2785 ASAP (latest by 4:00 PM PST on Monday, 07/18) in order to make it to M53 dev release next week before Beta promotion.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/7fb006083710f482493a5643509fedc6f399cd4a

commit 7fb006083710f482493a5643509fedc6f399cd4a
Author: Marc Treib <treib@chromium.org>
Date: Mon Jul 18 08:19:34 2016

Adding the creation_flags back to pending_extension_info. Add a unit test to cover the case when an external extension is updated before being installed and make sure it retains the creation flags.

BUG= 627522 

Review-Url: https://codereview.chromium.org/2146963004
Cr-Commit-Position: refs/heads/master@{#405856}
(cherry picked from commit 0128d5a9b0a402cd85aa0ef409c73f3ad1df548c)

Review URL: https://codereview.chromium.org/2158753002 .

Cr-Commit-Position: refs/branch-heads/2785@{#175}
Cr-Branched-From: 68623971be0cfc492a2cb0427d7f478e7b214c24-refs/heads/master@{#403382}

[modify] https://crrev.com/7fb006083710f482493a5643509fedc6f399cd4a/chrome/browser/extensions/extension_service.cc
[modify] https://crrev.com/7fb006083710f482493a5643509fedc6f399cd4a/chrome/browser/extensions/extension_service_unittest.cc
[modify] https://crrev.com/7fb006083710f482493a5643509fedc6f399cd4a/chrome/browser/extensions/pending_extension_info.cc
[modify] https://crrev.com/7fb006083710f482493a5643509fedc6f399cd4a/chrome/browser/extensions/pending_extension_info.h
[modify] https://crrev.com/7fb006083710f482493a5643509fedc6f399cd4a/chrome/browser/extensions/pending_extension_manager.cc
[modify] https://crrev.com/7fb006083710f482493a5643509fedc6f399cd4a/chrome/browser/extensions/pending_extension_manager.h
[modify] https://crrev.com/7fb006083710f482493a5643509fedc6f399cd4a/chrome/browser/extensions/updater/extension_updater_unittest.cc

Verified the merge on the latest M-53(53.0.2785.21 /2785@{212}) on Windows 10 and this is working as intended. Didn't observe any permission prompt under Wrench menu for Google Drive or Google Docs.


Marking this as Verified therefore.

Can we check this is fixed on todays build?

Powerwashed device and added user account. Permission prompts are not seen.

Verified on ChromeOS M53 beta (8530.35.0, 53.0.2785.36)