Extension Suddenly Removed!

[Chris Zalcman]

Today we received a removal letter from CWS. 

ID:  abjcfabbhafbcdfjoecdgepllmpfceif

Inaccurate description policy for not providing the promised functionality.
In the earlier version: 7.9.5.3, we are able to see an icon in the right bottom corner on a YouTube player from where the user can access the promised functionalities. However we couldn’t see that icon-based functionality in the recently rejected version(7.9.5.5). So, we kindly request you to provide the mentioned functionality.

This functionality exists, YouTube just changed its interface several hopurs ago! How could we manage to release a new version in an hour or two? But CWS wrote us today about a new "inaccurate description policy" and  immediately deleted Magic Actions form the CWS, that's why didn't give us time? This is not violation, this is  pressure on developers. We are members of the European Commission on IT issues, and if you continue to nitpick, we'll be filing a complaint against Google for putting pressure on developers.

We will of course upload a new version for a new YouTube interface, just give us time.

Someone here can help us restore the extension on the CWS (from 2011 year on CWS!)

 

Thanks for advance.

Magic Actions team.

[Patrick Kettner]

Hey Chris

That is surprising to hear. It is really unusually for an item to be delisted for what you are saying. Did you open an appeal on One Stop Support (https://support.google.com/chrome_webstore/contact/one_stop_support)?

I reached out to the review team to see what is going on, and it looks like the item was actually removed because of the warning you received on September 24. The removal was not related to the rejection of the last update you received. You should have received a few warnings about this date and the pending removal in the weeks between the initial warning and the final takedown. If and when you do submit an update that is accepted, the listed would be restored. Also, just so you know, the item isn't removed from any user's profiles as a result of this takedown.

thank you

patrick

[Chris Zalcman]

Hi Patrick,

 it looks like the item was actually removed because of the warning you received on September 24

No, yesterday we has been received from CWS thr following:

We reviewed your request and found that the previously enforced violations are rectified in the latest version from your end.

And, yesterday YopuTube changed the interface and some people from CWS imedialelly Taken Down extension for the:

is not compliant with our inaccurate description policy for not providing the promised functionality

By the way the previous allegations of violations were not such and we have proven it. 

So why was our extension actually removed? Actually for no reason.

We believe the European Commission will figure out what's going on here and why, by the way, 

Google is banning downloads from the developer's website? This is also a violation of the rights 

of other companies, at least in the European Union. We wouldn't want to do this, but since Google 

can't rein in its employees who are blatantly destroying competitors, we'll probably have to do it? 

Not to mention investors....

We still hope that Google will take reasonable action, and that the situation 

will be resolved quickly and immediately.

[Patrick Kettner]

Hey Chris,

> No, yesterday we has been received from CWS thr following:

Yes, the violation had been rectified, but the extension not working resulted in the item still not having a valid version to replace it. Once you get a take down warning like the one you recieved on September 24, a clock starts. If you don't have anything publishable by the time the clock hits zero, it is removed from the store. 

patrick

[Chris Zalcman]

Hi Patrick,

We have published the new version 7.9.5.5 before 30 day period starting september 24 and allegations of violations were not such and we have proven it. Yesterday YouTube changed the interface, and CWS imediatelly Taken Down our extension with a charge of a new violation! We don't have even a hour to correct anything. Please restore our extension as it was removed without reason, othrewise we will fill a complaint to the relevant EU bodies. If you continue to refuse to acknowledge your mistakes (no violations from our side, you konow this), I think this and many other things will be very displeasing to investors. Stop playing dumb, I hope that's clear?

[Chris Zalcman]

Thx Patrick for your support,

Just submitted the new version 7.9.5.6 which works correctly with the new YouTube interface, which was launched on Monday, How could we correct this in the previous version? We can't predict the future ;) It's still unclear for us why CWS removed the extension due to that.

We hope this version will be approved as soon as possible, as currently there is no magic button on the YouTube player at all and there are no new installs

[Patrick Kettner]

Hey Chris

I apologize for not being more clear. I will try to be so now

When an item has a violation, it is put into a "has-been-warned" state. The developer has a set period to update their listing and get the item out of that state. The time is not to fix the specific violation. If it were, a developer could play whack-a-mole by continually introducing new violations to keep an invalid listing on the store indefinitely. 

While your first violation was fixed, the update that resolved it introduced a new violation. This new violation was because of YouTube's update, which was clearly outside your control. However, from the reviewer's perspective, the item was broken. Because it is still in the "has-been-warned" state, the timer that began when the initial violation occurred reached zero, and so the item was delisted. 

That is why it occurred, but I agree that this process is unfair in this case. I don't believe this was a circumstance that was taken into account when these policies were created, and I am working with the review team and the Chrome Web Store leadership to both fix your specific listing as fast as possible, as well as figure out how we can update the rules to prevent similar problems in the future.

patrick