Issue metadata
Sign in to add a comment
|
master_preferences - Extensions not being installed
Reported by
pawlus.p...@gmail.com,
Jun 27 2018
|
||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.99 Safari/537.36 Steps to reproduce the problem: 1. Install Chrome for Enterprise (fresh installation on new device) 2. Create master_preferences in %programfiles(x86)%\Google\Chrome\Application with content of the full example (Pre-installing via master_preferences) on https://www.chromium.org/administrators/pre-installed-extensions 3. Start Chrome, wait some seconds and check the menu What is the expected behavior? Installation of extension "Google Reader Notifier" on Chrome startup. What went wrong? No extensions being installed. Did this work before? Yes 66.0.3359.181 Chrome version: 67.0.3396.99 Channel: stable OS Version: Windows 10 1703 Flash Version:
,
Jul 4
,
Jul 20
Hi team, An enterprise customer has reported the same issue as this case. Is there any update that can be shared with the customer? case#16241062
,
Jul 20
,
Jul 23
privard@ as yiningc@ commented previously, could you please assign this bug case to the master_preferences owner?
,
Oct 29
Greg, you were doing some work in this space. Can you comment on this?
,
Oct 30
rdevlin.cronin: has anything changed in the land of extensions since Chrome 66 that would break preinstalling extensions via master_preferences as documented in https://www.chromium.org/administrators/pre-installed-extensions? I've just tried with 70.0.3538.77 using the example on that page. While I see that OnExtensionSystemReady (https://cs.chromium.org/chromium/src/chrome/browser/first_run/first_run.cc?dr&q=OnExtensionSystemReady%5C(+file:first_run.cc&sq=package:chromium&g=0&l=161) is being called, the specified extension isn't installed. Thanks for taking a look.
,
Jan 11
Hello! This bug is receiving this notice because there has been no acknowledgment of its existence in quite a bit of time. - If you are currently working on this bug, please provide an update. - If you are currently affected by this bug, please update with your current symptoms and relevant logs. If there has been no updates provided by EOD Thursday, 01/17/19 (5pm EST), this bug will be archived and can be re-opened at any time deemed necessary. Thank you!
,
Jan 11
I am not currently investigating this. Do we know if this is still an issue?
,
Jan 11
,
Jan 14
It was an issue when I looked into it. Is there someone on the extensions team who could try out the documented process I mentioned in comment 7 and see what's going on? I don't know the extension system well enough to investigate further. Thanks.
,
Jan 14
Hi privard@ is there someone on the extensions team that could continue to investigate this issue?
,
Jan 17
(5 days ago)
Hi Devlin, We are receiving some feedback from some customers that this issue is persistent in more recent versions of Chrome. Can you please investigate as per #c7?
,
Jan 17
(5 days ago)
lazyboy@, I think you have a windows machine - can you investigate this and see if you can reproduce and find the point of failure? (We can triage further once we have a better idea what's going on) |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by yini...@chromium.org
, Jul 2