Force-installed extensions do nor get pushed properly |
||||||||
Issue description(See also b/22125694 for context.) I have a force installed extension (https://chrome.google.com/webstore/developer/edit/dbeighpjcdbikjklncomfcbgjjfdnhbj) that is being pushed through CPanel to all devices within an organization. However, when I update the extension in the store, it never makes it to my devices, even hours after it has been uploaded to the store and is visible there as the only version of the extension. Even with Developer mode checked in chrome://extensions, and clicking "Update extensions now," the extension doesn't update after a new version is available. I have to completely delete the extension and publish a new version as an entirely new extension with a new ID each time. This is a terrible experience for our customers in addition to the inconvenience to me (which we could disregard). It takes a LONG time from publishing to bing available in all the CPanel backends so that one can reliably add the "new" extension back in CPanel, not to mention its whole configuration needs to be redone at that point.
,
Apr 17 2017
,
Apr 17 2017
There is a class of enterprise extensions that only work when force-installed by policy (these are extensions using chrome.enterprise.platformKeys API, kiosk apps, and soon login screen extensions). We have observed update issues with these before (see the buganizer b/22125694), but it's really hampering our development efforts right now. Can we please investigate this issue with priority in order to unblock enterprise team (and avoid similar headache for the external extension developers)?
,
Apr 25 2017
You can force-update extensions under chrome://extensions -> Update extensions now.
,
Apr 25 2017
+jawag for prioritization / explanation
,
Apr 25 2017
Sorry. That does NOT work is what I meant to type....
,
Apr 26 2017
+omaha and chrome enterprise folk, any ideas?
,
Apr 26 2017
I need a net-internals trace during an attempt to update from chrome://extensions like you had in the internal bug: While that was helpful, it looks like you've since changed app IDs and the state of the other ID has changed, so I can't easily debug the issue. Alternatively, we can walk through the repro together when you get back in a couple weeks.
,
May 8 2017
Hi, I'm back. Do you want to come look at it with me?
,
Jul 19 2017
,
Jul 19
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jul 19
IIRC we looked at and resolved this.
,
Jul 19
How?
,
Jul 19
Don't remember, I don't remember what was wrong. I'm guessing it was something about public / restricted apps, since I faintly recall that you worked around it by just making your app public. |
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by drcrash@chromium.org
, Apr 14 2017Labels: -Pri-3 Pri-2