Rejected by the Chrome web store - "Hidden logic"

Edit Subject

Thanks Titus for reporting this.

Your code does appear in the WebStore package though you are right in your assumption that the engine also pulls the code from the cloud after installation. (To make sure your code is up to date).

I have noticed that you have minified your code, so it might be the reason for the rejection, in that case, making your code un-minified could help.

In any case we will investigate this on our end as well.

Titus,

We had done some tests and everything is looking OK on our end.

Can you please de-minify your code (make it clean and readable) and try to re-publish again on the Chrome Store ?

Please keep us posted with the results.

Shmueli,

I have resubmitted a non-compressed version of my extension. It is currently In Review, I will report back with the result. Thanks for the prompt replies!

Here's my followup.

I've resubmitted my extension four more times. The rejections are still coming, always with the same message as the first. Since I posted last I have revamped my build process, and am no longer uglifying the code in any way. For the last submission we added custom post-install thank you page and a support URL in the google form, hoping that info would help make it a little more clear what the extension does.

I understand where someone could look at the code and feel that it's missing something; the extension is designed to work with our platform and won't really do much until a user interacts and chooses to activate the plugin. We're functionally complete right now and are evaluating what to add next to help get it into the Chrome store. Any suggestions you would have would be appreciated.

Titus,

This is indeed very odd.

Can you please forward the rejection email to support@crossrider.com so we can get more information regarding the issue you are experiencing.

We can continue this discussion in more details from there.

Time for a Good Internet Citizen update. I was finally able to circle back to this and work on getting the extension accepted.

We did a combination of things. Including the aforementioned lack of uglification, we also refactored parts of the code to be more legible, made sure all the dev comments were still in the codebase, added a post-install thank-you page, added a Support page in the chrome store, and lastly enabled a browser button for Chrome users. The button promotes some fluffy user interaction that, while not required right now, we will build upon later as we add features. We also re-submitted with a brand new Google dev account.

This time around the extension was accepted and pushed live almost instantly. I was able to do a couple of updates in the Chrome store without issue, everything appears to be fine now.

We don't know exactly what combination prevented our submission from being flagged. The popup adds a decent chunk of code to the extension as well as some obvious interactivity. The account we were using had also been around for a while, and had been used with a wide variety of Google services. I suspect it was a combination of possibly a flag on the account and our extension being rather bare-bones.

Thanks for the help, and the framework!

Titus,

This indeed the spirit of a good citizenship ;)

We appreciate the update and glad to hear the good news!