2
2 Comments

Has anyone been able to submit a paid Chrome Extension on the Google Web Store?

I've submitted the same Chrome Extension with a custom payment solution three times in the past month (after changing the icon and screenshots each time), but it keeps getting rejected with:

Your item did not comply with the following section of our Program Policies:

"Spam and Placement in the Store"

Item has a blank description field, or missing icons or screenshots, and appears to be suspicious.

I have descriptions, icons, and screenshots. I've replied to the rejection twice asking for more details. I've gotten the original rejection message as a response both times.

The code is simple, clear, and less than 650 lines.

I'm wondering if it has something to do with Google cleaning up the Web Store. They're trying to remove all the spam and scam extensions. They've also put a block to any new paid extensions coming through. Read more here: https://www.theregister.co.uk/2020/01/27/google_disables_web_store/.

I don't know if I need to improve the description, icon, screenshots, or the code - they're all completely different - or if it's because of the paid extension block.

I've got preorders for the extension. It's frustrating not being able to get it out to users.

Has anyone had a successful experience publishing a paid extension to the Google Web Store within the last few months?

on March 18, 2020
  1. 2

    Hey!

    Check out the official dev support group here - https://groups.google.com/a/chromium.org/forum/#!forum/chromium-extensions

    I'm reading ongoing conversations there. It seems that paid extensions won't work properly. Consider switching to Stripe/whatever 3rdparty solution

    You should push hard to get the store; payments work really bad e.g. not charging users in February because it has < 30 days

    PS Check if you have 128x128 icon, it's required now for some reason and you get rejected

    1. 1

      That's a great resource, thanks for sharing it :)

      After looking at that forum, I'm definitely not the only one experiencing this problem.