New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 845212 link

Starred by 3 users

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

Chrome Extension installed using Windows Registry doesn't show notification popup to enable extension

Reported by parthivs...@gmail.com, May 21 2018

Issue description

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

Steps to reproduce the problem:
1. Execute msi which adds entry into registry for CWS hosted extension.
2. Verify notification popup is shown to enable extension.
3. Execute upgraded msi which removes previous registry entry and adds new registry entry for newer extension (both extensions have different ids).
4. Verify at this time notification popup to enable extension is not shown.
5. Restart the chrome and verify notification popup is not shown. 

What is the expected behavior?
When old registry entry is removed and new registry entry is added, notification popup to enable extension should be shown.

What went wrong?
For newly added registry entry popup is not shown and it looks like extension is blacklisted without user interaction.

WebStore page: 

Did this work before? N/A 

Chrome version: 66.0.3359.181  Channel: stable
OS Version: 7
Flash Version:
 

Comment 1 by ajha@chromium.org, May 22 2018

Labels: Needs-Triage-M66
Cc: sindhu.chelamcherla@chromium.org
Labels: Needs-Feedback Triaged-ET
@Reporter: Please provide sample extension to reproduce this issue from TE end. If possible please attach a screencast on reproducing this issue.

Thanks!
Old extension is : 
https://chrome.google.com/webstore/detail/saba-org-planning-chrome/bblkdmbomjhcoigilagamgllfhclkpbg
New extension is :
https://chrome.google.com/webstore/detail/saba-org-planning-chrome/hphcadhmjbledohfmbioeidgoafljehi

I have also attached screencast so that issue can be reproduced.
test.7z
5.7 MB Download
Project Member

Comment 4 by sheriffbot@chromium.org, May 22 2018

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
I have created Sample msi files for old and new version which I have attached here. steps to reproduce issue:
1. Open chrome in windows.
2. Open some random tabs.
3. Execute SampleSetup_old.msi.
4. Enable extension by responding notification popup.
5. Close chrome.
6. Reopen chrome and open some random tabs.
7. execute SampleSetup_new.msi.
8. Observe extension notification popup is not shown.

I have observed sometimes notification popup is shown especially when I go to extension url and manually download, install and then remove. ( This way extension is whitelisted).
SampleSetup.zip
56.7 KB Download
Labels: Needs-Feedback
Tested the issue on 66.0.3359.181 using Windows 10 with steps mentioned in comment#5, 1. On executing old .msi, not observing popup immediately, it is seen under wrench menu , enabled it from there.
2. Now again installed new .msi file and not observing any pop up file -- not observing    popup and not seeing in wrench menu as well.

@Reporter: Could you please check the screencast and let us know if we miss anything. Could you please let us know if this is the behavior you are observing.

Thanks!
845212.mp4
10.0 MB View Download
This is the behavior we are observing. Chrome should show notification popup to enable extension after installing new msi. It looks like an issue.

Thanks for reply!
Project Member

Comment 8 by sheriffbot@chromium.org, May 24 2018

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Cc: phanindra.mandapaka@chromium.org
Labels: M-68 Target-68 FoundIn-68
Status: Untriaged (was: Unconfirmed)
Able to reproduce the issue on reported chrome version 66.0.3359.181 and on latest chrome 68.0.3440.0 using Windows 7 & 10.

Note: This issue is applicable to only Windows. 
 
Same behavior is seen on M60(60.0.3112.113) hence considering it as non-regression and marking it as Untriaged.

Thanks! 
Owner: lazyboy@chromium.org
Status: Assigned (was: Untriaged)
lazyboy@ investigated some of this code awhile back; lazyboy@, mind taking a look?
Any updates on this issue? As this issue is severe for us as it prevents smooth user experience. can you please give me estimated time to fix or workaround for this issue?

Sign in to add a comment