Completely normal unfortunately and I get the same issue with my extension that has lots of users and a good rating [1].
Check out the Chrome extensions newsgroup and you'll find that instead of technical issues being discuss it's message after message of "Why is it taking weeks for my extension to be approved?" even when all that changed was the description.
I'd be up for joining/starting a petition at this stage - it's making extension development really unpleasant. There's no good reason why changing the description or changing a single line of code should take weeks of review time.
If you have a critical bug in a paid Chrome extension, what are you supposed to do? Do the big Chrome extensions like Grammarly and LastPass get special treatment? If LastPass has a security vulnerability, will Google really make them wait weeks to update their extension?
Your comment made me remember, the first time my extension took more than 3 weeks in review was when the description was "improved". There weren't any code changes, it's totally insane and as you said, it makes developing chrome extensions unpleasant.
Yeah, plus the Google team on this won't give much away about what the review process involves either because they say it'll give too much away to attackers. I can't see how there can be any justification for taking weeks to review a description change. It feels like the review system is really broken and they don't care.
Comments
Completely normal unfortunately and I get the same issue with my extension that has lots of users and a good rating [1].
Check out the Chrome extensions newsgroup and you'll find that instead of technical issues being discuss it's message after message of "Why is it taking weeks for my extension to be approved?" even when all that changed was the description.
I'd be up for joining/starting a petition at this stage - it's making extension development really unpleasant. There's no good reason why changing the description or changing a single line of code should take weeks of review time.
If you have a critical bug in a paid Chrome extension, what are you supposed to do? Do the big Chrome extensions like Grammarly and LastPass get special treatment? If LastPass has a security vulnerability, will Google really make them wait weeks to update their extension?
[1] https://www.checkbot.io/
Your comment made me remember, the first time my extension took more than 3 weeks in review was when the description was "improved". There weren't any code changes, it's totally insane and as you said, it makes developing chrome extensions unpleasant.
Yeah, plus the Google team on this won't give much away about what the review process involves either because they say it'll give too much away to attackers. I can't see how there can be any justification for taking weeks to review a description change. It feels like the review system is really broken and they don't care.