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

Issue 590482 link

Starred by 2 users

Issue metadata

Status: Archived
Owner: ----
Closed: Mar 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

new extension disabled

Project Member Reported by wfh@chromium.org, Feb 27 2016

Issue description

<b>Version: <Kenneth, what is the frequency?></b>
<b>OS: <please tell me it's not XP></b>

What steps will reproduce the problem?
1. Create a new extension.
2. Publish to chrome store
3. Wait for it to appear.
4. Add it in your Chrome.
5. Reload Chrome. It gets removed.

What is the expected output? What do you see instead?

Extension published in store shouldn't get removed

Please use labels and text to provide additional information.

 
removedextension1.png
19.1 KB View Download
Owner: asargent@chromium.org
Status: Assigned (was: Untriaged)
What's the extension id?

Assigning to asargent@ for investigation.
For the webstore lockdown, anytime we notice a new extension being added to a user's profile we send a request to a webstore API endpoint to ask if this is an extension id that's known to be in the store. When a developer publishes the first version of a new extension in the webstore, apparently there can be a slight propagation delay (on the order of a few minutes IIRC) between when it's available for installation and when the id becomes known to the API endpoint, so you can get the glitch of it being considered not in the webstore. 

I think I noticed this in the past and asked the webstore folks about it, and IIRC the answer was that it would be fairly difficult to fix. Since in practice this only affected developers who publish a new thing to the webstore and then immediately install it themselves, and goes away within a few minutes, it was deemed not worth the effort. 

Does the above match the circumstances where you saw this? Does the problem go away after 5 minutes or so?

Cc: asargent@chromium.org
Labels: Needs-Feedback
Owner: ----
Status: Available (was: Assigned)
Project Member

Comment 4 by sheriffbot@chromium.org, Mar 10 2017

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been available for more than 365 days, and should be re-evaluated. Please re-triage this issue.
The Hotlist-Recharge-Cold label is applied for tracking purposes, and should not be removed after re-triaging the issue.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Cc: rdevlin....@chromium.org
Status: Archived (was: Untriaged)
Archiving given the explanation in #2 and no further comment.  Feel free to reopen if there's any new information.

Sign in to add a comment