Very long extension moderation process

[tnowak]

tnowak Opera last edited by

@kurtq, @adsfactory-russia: Different stores have different acceptance criteria.
It means that in our store you can find extensions that would not be published in Chrome Web Store.

[A Former User]

A Former User @tnowak last edited by

@tnowak Thanks for the clarification, we understand you. Our technicians completed the amendments for the extension 231350. We will be very grateful to you for re-checking, if it does not complicate you.

[kurtq]

kurtq @tnowak last edited by

@tnowak I don’t understand why my extension is not suitable for your store?

[brainierweb]

brainierweb @tnowak last edited by

@tnowak If the extension does not meet any criteria - why is it not rejected? Wouldn't it be better to reject the addon and list the reasons for the rejection, instead of leaving the app in the "Awaiting moderation" status?
My package (237425) has been waiting for publication for several months. He may also have some criteria violations that I don't notice. However, I cannot know this. The app does not publish, but does not reject. He is just "waiting" for no apparent reason.

[A Former User]

A Former User last edited by

@brainierweb said in Very long extension moderation process:

@tnowak If the extension does not meet any criteria - why is it not rejected? Wouldn't it be better to reject the addon and list the reasons for the rejection, instead of leaving the app in the "Awaiting moderation" status?
My package (237425) has been waiting for publication for several months. He may also have some criteria violations that I don't notice. However, I cannot know this. The app does not publish, but does not reject. He is just "waiting" for no apparent reason.

Exactly. We finally got an Opera representer in this thread... How come it took so long?

[tnowak]

tnowak Opera @kurtq last edited by

@kurtq : Upgrade your jQuery to a version without vulnerabilities.
https://nvd.nist.gov/vuln/detail/CVE-2019-11358

[tnowak]

tnowak Opera @brainierweb last edited by

@brainierweb:
Your extension didn't use i18n, so the description in Russian was recognized as English. It would be great if you included some description in English too.
https://developer.chrome.com/apps/i18n

Published.

[brainierweb]

brainierweb @tnowak last edited by

@tnowak The posting is certainly great. However, my question remained unanswered: Why did the process take so long?
I have a very short release cycle. And waiting for each update for several months does not suit me. I want to know what causes the delay to correct them. Missing Description in English is the only violation?

[A Former User]

A Former User @tnowak last edited by

@tnowak Hi, please tell me, can the main description be in Russian? Extension 231350 will be used only on the Russian segment. Or should the description be in English?

[tnowak]

tnowak Opera @brainierweb last edited by

@brainierweb:
Our moderation queue is integrated with the points system mentioned by @tprockow. We are in the process of fine-tuning its parameters to give priority to good or popular extensions, yours included. It should be much better now.

[tnowak]

tnowak Opera @Guest last edited by tnowak

@adsfactory-russia: It's OK, but don't mix languages in different fields.
I see that you are discussing the rest of issues with our moderation team.

[A Former User]

A Former User @tnowak last edited by

@tnowak Thanks for the answer. Our technicians corrected all the points indicated by the moderators and we uploaded the new version. I hope the moderators can find a little time and re-check the corrections

[A Former User]

A Former User last edited by

Hi! We've been waiting for moderation since 2017. It there a way to find out what's the problem with it?

[kurtq]

kurtq @tnowak last edited by

@tnowak Thank! I downloaded the new version, the jQuery library was updated to the latest version, minor bugs were fixed. I hope that moderation will happen anyway

[oktools]

oktools last edited by

Hi. Why is my extension published for so long? The previous version has stopped working. Many corrections have been made. Users complain.
Enabled option "I want my extension to be available for auto-publishing."

package/21805
OkTools - v4.2.3 was submitted. Awaiting moderation.
oktools; Jun 7, 2019 8:46:32 PM UTC

[A Former User]

A Former User @tnowak last edited by

@tnowak You can say that with package/198615?

[tnowak]

tnowak Opera @Guest last edited by

@commaticus : Let's start with:

• "There must be no unused files."
• "Well-known third-party libraries must be in a genuine and in an unchanged form. They should be acquired from the vendor’s official website or a CDN."

[kurtq]

kurtq last edited by

Hello! Today version 1.7.7.2 was checked and rejected, all corrections according to your recommendations were made in the updated version 1.7.7.3. Please check 1.7.7.3, thanks

[tnowak]

tnowak Opera @kurtq last edited by

@kurtq : That's why the old version was rejected
And the review of the newest version is in progress.

[A Former User]

A Former User @tnowak last edited by

@tnowak
"There must be no unused files." - It seems there are no unused files.
"Well-known third-party libraries must be in a genuine and in an unchanged form. They should be acquired from the vendor’s official website or a CDN." - we use two libraries - jquery and D3js. They in a genuine and in an unchanged form. And they acquired from the official website.