How to Handle a Chrome Extension Rejection Summary 9 times from 26th Feb 2019 until it was accepted into the Chrome Store on the 1st of April. Because you will likely go through this process multiple times. “Can you provide more information about why this failed the review and what I have to do to fix it?” Since you receive the rejection in an email. This doesn’t help, but it makes you feel less alone. If you Google the error message you will see other people in the same situation. The Quality Guidelines are too vague to be any help. Please reply to this email for issues regarding this item removal. > If you’d like to re-submit your item, please make the appropriate changes to the item so that it complies with our policies, then re-publish it in your developer dashboard. Your app must comply with Google’s Webmaster Quality Guidelines For example, you cannot post an app if its primary function is to launch a desktop app that the user has already installed.Īnother example of a disallowed practice would be to post a packaged app that just launches a website. Your item did not comply with the following section of our policy:ĭo not attempt to change the placement of any Product in the store, or manipulate any Product ratings or reviews, by unauthorized means, such as fraudulent installs, paid or fake reviews or ratings, or offering incentives to rate Products.ĭo not post an app if the primary functionality is to link to a website not owned by the developer posting the app.ĭo not post an app where the primary functionality is to install or launch another app, theme, or extension. Reasons for Chrome Extension Rejectionĭear Developer, Your Google Chrome item, “…” did not comply with our policies and was removed from the Google Chrome Web Store. Watch on YouTube What if your Chrome Extension is rejected?īoth of my Chrome extensions were rejected by the Chrome store.įor the same generic reasons. I’ve created a video showing the release process in action. Video showing how to release a chrome extension added a YouTube video showing the plugin in action.Paste in all the descriptions, icons and screenshots “Add New Item” from the Chrome Developer Dashboard I created a separate google account because the developer email address needs to be publicĬreate a zip file of the extension, I zipped my code so that the manifest was in the root of the zip i.e. I created an icon in Gimp - 128x128, 48x48, 16x16Ĭreate screenshots for the application of 1280x800 or 640x400 Up to date instructions and directions will be on the Chrome Store: You can find the code for both my Chrome Extensions on Github and you’ll see all the images, descriptions and manifest files that I created there if you want to model my final submissions. I have a video showing the full process at the bottom of the post. I’ll describe that process in a later blog. I have described the basic process for releasing the extension.Īfter following this process you may have to refine your entry if it is rejected during the submission process. Neither went in first try, but both eventually made it after adjusting the description and adding some more screenshots. I have now released two extensions to the Chrome Store. In this post I describe the steps to release an extension. Writing a Chrome Extension is pretty easy (getting it in the Chrome Store is much harder!).
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |