Make sure that Chrome loads a packed version of your extension as expected by manually packing your extension and dragging the generated.
Unpacked and packed extensions can have different behaviors. This may mean extracting resources from the package that you submitted. Test the exact files that you submit to the web store, not just a local development version of your extension. #GOOGLE CHROME WEBSTORE KC3 KAI CODE#
Test the code that you submit to the web store locally. Your item is just not functioning as it expected based on the item's listing. A functionality in your item is not working due to a server side issue at the time of reviewing. The path or name of the files mentioned in your package are incorrect. This is most commonly seen with image files. There are files mentioned in your manifest that are not present in your package. Extensions should provide the functionality described in their listings and, if they cannot, communicate that to the user. The intent of this policy is to ensure a minimum quality level for all items published in the Chrome Web Store. # Functionality not workingĬorresponds to notification ID: Yellow Magnesium For example, Yellow Magnesium corresponds to the general class of errors where the extension does not behave as expected. These IDs are composed of two words: a color and an element. In order to make it easier to reference specific violations, the Chrome Web Store assigns each violation a human-readable ID. 
This page is provided to help you understand why your extension was rejected or removed from the Chrome Web Store and how you can fix the violation.Įach section in this document describes the issues that correspond to a particular category of violation.
0 kommentar(er)
