Extension is disabled because of permission changes that don't exist when rolling out a new version
Reported by
n...@joinhoney.com,
Feb 7 2018
|
|||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.140 Safari/537.36 Steps to reproduce the problem: 1. A new extension update (version 1.1) is being rolled out to a staged percentage of devices. (set to 1%) 2. A user with the old extension (version 1.0) installed on a device logs into the same Chrome profile on another device. 3. The new device now syncs all extensions, and during the sync the new device gets the new extension (version 1.1). 4. The version of the extension on the new device (version 1.1) differs from the version on an old device (version 1.0), because of the rollout/sync. 5. The user now has two different versions on two different devices while being on the same Chrome profile. The manifests for these extensions are now different when compared. Result: The user receives a popup notification on the new device stating that they need to re-enable the extension because the permissions have changed, even though the permissions themselves have not changed. What is the expected behavior? The extension would remain enabled and would update without the user having to re-enable it, as there were actually no permission changes with the extension. What went wrong? A certain percentage of our users are prompted to re-enable the extension because of permission changes, even though the extension permissions have not changed. WebStore page: https://chrome.google.com/webstore/detail/honey/bmnlcjabgnpnenekpadlanbbkooimhnj?hl=en-US Did this work before? N/A Chrome version: 64.0.3282.140 Channel: stable OS Version: OS X 10.13.3 Flash Version: Not sure if this is the right place for this issue or if its a chrome web store issue.
,
Feb 7 2018
,
Feb 7 2018
,
Feb 7 2018
,
Feb 15 2018
Checked the issue on reported chrome version 64.0.3282.140 using Mac 10.13.1 with the below mentioned steps. 1. Launched chrome 2. Navigated to https://chrome.google.com/webstore/detail/honey/bmnlcjabgnpnenekpadlanbbkooimhnj?hl=en-US We are able to see a different version of the extension when compared to that of info given in comment#0. Attaching the screen shot of the same. @Reporter: Could you please check the screen shot and let us know if we have missed any thing in the process of reproducing the issue.
,
Feb 15 2018
Hi. The versions listed above were used as examples that could be reproduced with any extension. One of the specific instances we saw it happen with the Honey extension was when we were rolling out the release to 10% of users, from 10.6.1 to the current 10.6.2.
,
Feb 15 2018
Thank you for providing more feedback. Adding requester "vamshi.kommuri@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Feb 19 2018
,
Apr 13 2018
Thanks for reporting! We haven't been able prioritize looking into this issue yet.
,
Jun 7 2018
The underlying issue here is that we don't actually sync the approved permissions - we only sync the version and that fact that it was approved. So the second device only knows that it has version 1.1, but only version 1.0 was approved, so it doesn't know if there are any new permissions. Devlin, I believe you've been looking into this recently - are there any news on actually syncing permissions? Also, we probably have an existing bug that this one could be duped against.
,
Jul 9
Triage ping: rdevlin.cronin@, could you please address questions from #11?
,
Aug 6
sync-triage ping: any updates?
,
Sep 9
sync-triage-ping, any updates?
,
Oct 29
I suspect this is the right bug for this. I use the Google Hangouts extension and it's continually disabled due to requiring me to accept "new" permissions, even though nothing has changed. It might be version skew across browsers (though I'm not sure how) or it might be that the extension is disabled after browser updates. I regularly use the same profile on a variety of devices and Chrome versions for testing and development. The most annoying part is that the only way to tell that the extension is disabled is because the icon is missing and clicking a hangouts chat in gmail opens a window in gmail instead of the extension window. There's never a notification to re-enable, and I have to go find it in chrome://extensions.
,
Jan 15
rdevlin.cronin@: triage ping, thanks. |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 Deleted