After that period expires, the staged submission will revert to a draft which will have to be submitted again for review.

Once the review is complete, you will have up to 30 days to publish. This lets you wait until you are ready (for example, with marketing announcements) and then manually publish it at a time of your choosing. Instead, after it passes the review your item will become ready for you to publish. If you uncheck the checkbox, your item will not be published immediately after its review is complete. This dialog also lets you control the timing of your item's publishing.

The following dialog appears, letting you confirm that you want to submit the item for review.

Make sure you've completed the details on all the tabs described above.

When an update requires additional permissions, users will be prompted to accept them or disable the extension. This allows you to gradually roll out your item to ensure that any unexpected problems will have minimal impact. If your item has a large user base (over 10,000), the distribution tab will include a Percentage rollout option to restrict the update only to a fraction of the user base:

The Payment and Distribution tab lets you declare in-app purchases and control which countries will list your item and which set of users will see it.

The Privacy tab is where you include declarations about how your item uses privacy and security related features.

The Listing tab contains details of your listing and how it should display in the Chrome Web Store.

You update this information on the same tabs used for creating a new item:

If you're changing anything about the Chrome Web Store listing for your item, its distribution, or details of your privacy policy, you must update the information on the developer dashboard. In the developer dashboard entry for your item, on the Package tab, use the Upload New Package button to upload the zip file: # Update the listing metadata Each new version must have a larger version number than the previous version. Make sure you increment the version number. If you're changing any code, the manifest, or other assets packaged with your extension, you must make a new zip file and upload the new package. Make sure you follow these guidelines to avoid being flagged as Repetitive Content. The Chrome Web Store allows the publication of testing and production versions.

Upgrade google chrome to latest version