PSA: Increase in review times for submissions to the Chrome Web Store

[Sebastian Benz]

Hey everyone,

I want to provide an update on the current state of extension reviews in the Chrome Web Store. We’ve experienced a surge in new extensions being submitted to the Chrome Web Store causing longer-than-expected wait times for new submissions and updates to be approved. We are aware that predictability in the review process is crucial for your planning. We sincerely apologize for this friction and appreciate your patience during this time.

While our review team works to process the queue, we recommend the following best practices to help expedite your specific review and avoid unnecessary resubmissions:

• Schedule Publication in Advance: Please build additional buffer time into your release cycles and submit early for important updates. You can stage your release so you can put it live at a time of your choice.

• Do Not Resubmit Pending Items: Refrain from canceling and resubmitting pending items in an attempt to speed up the process. Doing so resets your position in the queue and will always be slower than waiting for a response on your current submission.

For new extension submissions you should also check the following:

• Minimize Permissions: Audit your extension before submission to remove unused permissions. For example, use the activeTab permission or optional host permissions to reduce the access your extension needs immediately at install time, which can speed up review.

• Review Permission Usage: Check the list of commonly misunderstood permissions to ensure you are using them correctly.

• Clean Up Code and Files: Don't include unnecessary files or dead code in your submission. This can slow down review, make your extension a larger download, and unused code can even lead to rejections if it violates policies.

• Remove Remote Hosted Code: Check for Remote Hosted Code before submission.

• Verify Contact Information: Make sure you can receive emails from all email addresses associated with your Developer Dashboard account and publisher, as this is where rejection emails and warnings are sent.

• Check URLs: If you provide a privacy policy on your listing, ensure it is up to date and the URL works, as broken links are a common reason for rejection.

Thank you for your patience,

Sebastian, on behalf of the Chrome Web Store team

[Jack]

To give you some perspective on how you're affecting your bigger developers I get over 200,000 installs a month and right now I'm trying to release a fix for a bug that causes all those new users to have an issue and unfortunately now there's nothing I can do other than wait 28 days. Thanks a lot.

[RoEarn]

I just want to also highlight that it is extremely unfair if a bunch of new users submitting new extensions with no history cause developers with history, large user-bases, and featured badges to be delayed. Your existing users should always be your priority, because pushing updates is way more crucial than releasing a brand new extension. There's no doubt that updates to existing extensions should have priority in queue then new extensions do.

On Thursday, April 23, 2026 at 6:53:52 p.m. UTC-4 Sebastian Benz wrote:

[Jack]

Why are brand new extensions causing old extensions with large user bases to be delayed? This needs to stop this can't be happening because we're living in the time where AI is being used now and anyone can code an extension so we're going to see a lot of new extensions coming. This is not the way we want to go with the review system guys. Chrome Web Store team needs to rebuild their review system to prioritize updates being pushed from existing extensions. Why are we building up our extensions, getting featured, just for us to get no priority review time and be delayed. You're basically insulting us.

"We’ve experienced a surge in new extensions being submitted to the Chrome Web Store causing longer-than-expected wait times for new submissions and updates to be approved."

On Thursday, April 23, 2026 at 6:53:52 p.m. UTC-4 Sebastian Benz wrote:

[RoEarn]

Hey Sebastian,

Thank you for providing more information about this, though none of the important questions were answered here and this doesn't really provide any information.

1. When can we expect it to go back to the regular review times?

2. Why should large user extensions not have an advantage and faster position in queue than for example new users who are submitting brand new extensions with no history?

3. Should users be able to pay a yearly or monthly fee to get expedited review times like $99 or something for companies and developers that don't have time to waste? (Apple does something similar)

Just because you guys are the number one extension platform in the world doesn't mean you should get comfortable with horrible review times because you know we're going to be forced to use your platform anyways.

There's businesses that are generating millions of dollars in revenue a year using your platform and there's no reason why it should take 28 days for a simple change to the code to be released. This is a huge let down to your users and honestly extremely inconvenient. The worst part is you betrayed our trust. For years we've gotten used to the routine in your review system so we know how to push updates, but now you've just randomly changed it with no notice and now it's just randomly taking 30 days.

Do better team. We love you and rely on you.

On Thursday, April 23, 2026 at 6:53:52 p.m. UTC-4 Sebastian Benz wrote:

[Sebastian Benz]

Thanks for the feedback and suggestions Svetlana. I understand that you're unhappy about the current situation (we're as well!). We hope to resolve the situation over the following weeks - this definitely should not be the new normal. We're actively discussing and investigating different approaches on how we can avoid this situation in the future (and you're suggestions are part of what we're discussing), but there's nothing concrete yet that we can share. 

[Incarnae]

I don’t think “schedule your publication in advance” is a reasonable answer here. If it’s a bug, by definition you don’t know it exists until it’s already live. At that point, telling developers to wait through long review times again isn’t a solution it just compounds the problem. I also agree with Jack’s point. There needs to be a clear distinction between brand new extensions and established ones with large user bases. Many of us depend on our extensions for income, and delays like this can directly translate into financial loss. It’s hard to understand how a multi billion dollar company can’t balance this better.

I want to echo what Jack said because it’s exactly the core issue here. Why are brand new, low usage (and often AI generated) extensions being reviewed in the same queue as updates to established extensions with real user bases? That doesn’t make sense. Updates to existing extensions, especially ones impacting active users should be prioritized, not delayed behind a flood of new submissions.

The tiered system idea is exactly what’s needed. Many developers would gladly pay a yearly fee for faster reviews. Right now, high impact updates are being delayed behind low impact, often unused submissions that’s backwards and needs to be fixed.

--
You received this message because you are subscribed to the Google Groups "Chromium Extensions" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-extens...@chromium.org.
To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/chromium-extensions/2ca5dc77-4e9a-49da-8800-3286a213ae3cn%40chromium.org.

[Lucas]

We used to confidently tell users that the Chrome Web Store had the fastest review times, while the Edge Add-ons Store often required a week or more.

Recently, this appears to have reversed: Edge reviews have become significantly faster, while Chrome Web Store submissions have remained pending for over three weeks with no progress.

I understand the increasing review pressure driven by the growing volume of extensions. However, this level of delay is becoming a practical issue for developers—especially considering that submissions exceeding three weeks are already considered abnormal and require support escalation .

A more scalable approach would be to introduce:

• A tiered review system prioritizing established or high-impact extensions
• An optional paid fast-track review for developers

These measures could better balance security, efficiency, and ecosystem growth.

Thank you for your continued efforts, and I hope to see improvements soon.

[Jack]

Dear Sebastian and other Chrome Web Store team,

Since you guys are aware that this is a problem, and that this shouldn't be happening, and that this is affecting your developers, why are you not providing assistance to bigger developers trying to push crucial updates right now but can't? Instead, you're basically just telling them that they have no other choice than to wait.

The least you guys could do, temporarily, is allow for the request of expedited reviews via the One Stop Support forum, because you guys are aware that this is a problem, so you should be helping your users out while you fix it. Please take this into consideration.

[Jack]

Well, since we need to get into survival mode I've changed my website home page to a status tracking when you guys are going to review the extension.

And all these hundreds of angry emails from my users are slowly calming down because I'm giving them free $5 USD balance credit (for my platform) in exchange for their patience for Google to review the extension.

Gonna try to sleep through the next 28 business days  (Holidays not included)  to make it go by faster.

On Saturday, April 25, 2026 at 12:28:11 a.m. UTC-4 Lucas wrote:

[Yannick Kamin]

Dear Developer,

Thank you for reaching out and sharing your feedback regarding the current review times and the impact these delays have on your development process. I understand the frustration caused by these wait times, especially for critical bug fixes affecting your user base.

I am currently gathering information regarding the status of the review queue and the possibilities for addressing critical updates. I will return to you within 24 hours with a more detailed response.

Thank you for your patience.

Best regards,
Yannick Kamin

Email sent via Mail Agent

[Zhongbin Ning]

Hi Chrome Web Store Developer Support Team,

I'm writing to follow up on a critical review delay affecting my extension (ID: nmgfpjbckmbhpndgpmkbgbmopnkigncc), which has over 7,000 active users.

My extension hit a critical bug that made it completely non-functional for users. I submitted a fix several days ago, but it has not yet passed review. Historically, my updates are approved within a few hours — this wait is highly unusual for me.

What makes this especially confusing: another extension I maintain was submitted around the same time and was approved within 30 minutes. This suggests the delay may be specific to this particular extension or submission, rather than a general backlog.

The impact is significant — users have been unable to use the extension for days and continue to report the issue. Every additional day of delay directly erodes user trust and retention.

I understand the review team handles high volumes of submissions, and I appreciate the work they do. However, given the critical nature of this bug fix and the number of users affected, I'd like to respectfully request that this submission be prioritized or manually reviewed.

Submission details:
- Extension ID: nmgfpjbckmbhpndgpmkbgbmopnkigncc
- Developer email: ning...@gmail.com
- Issue type: Critical bug fix
- Active users affected: 7,000+

Thank you for your time and support. I look forward to hearing from you.

Best regards

[Jack]

Thank you, we are all hoping to hear back from you soon regarding this situation. 

This is a living nightmare currently and shouldn’t be happening. We are all relying on, and trusting your platform to run our businesses which we invest our own hard earned money into. 

There’s nothing we can do other than hope you guys fix it. I’m grateful that the Chrome web store team does have enough empathy to realize how bad this is for devs. 

Please fix it ASAP. We as developers of the extensions have a huge responsibility, but so do you.

[Jordi Salvat i Alabart]

Hi Sebastian.

It would be very helpful, in coping with this situation, to have visibility of the current review times. Precise delays for each of the queues you may have would be ideal, but even a current average would be helpful. Otherwise we're always in doubt of whether our extension has fallen into some special crack and we should write to One Stop Support or maybe even cancel and resubmit.

Understanding the review process and what factors may impact its length (and hopefully by how much) would also be useful. For example: a few years ago we received hints that host "*://*/*" permissions would increase review times -- we were even planning to recode some functionality (at a loss to our customers & our business) to avoid those permissions, but since there was no clear statement, we never did. Maybe such clarity could encourage developers to make changes to make your review easier -- hence helping you reduce the necessary review effort to keep the queue in check.

Hope these suggestions help.

Regards,

Jordi

El dia dimarts, 28 d’abril del 2026 a les 4:57:36 UTC+2, Jack va escriure:

[Resell Track]

Hello,

I'm reaching out regarding my Chrome extension currently stuck in review.

Extension: ResellTrack
Extension ID: pbbbhbhcaiepibbalaoecnnkhemcmmdb
Version: 1.2.0
Submitted: April 22, 2026
Current status: Pending Review (6 days)

The extension has been in "Pending Review" status since April 22nd. Previous versions were reviewed within 24 hours, so this delay seems unusual and likely indicates a manual review was triggered.

Could you please check on the status of this submission and let me know if any action is required on my end?

Thank you for your time.

Thomas

[Dan Makarov]

@Sebastian Benz: Would you mind posting a daily update on the situation?

For many companies doing B2B extensions there are SLAs in place with customers, so the delay is not just an inconvenience, but an actual cost.

Customers rely on us, we rely on Chrome Store, Chrome relies on good extensions to deliver a great experience with the minimal amount of bugs.

Thank you in advance!

[Inssist App]

Dear Sebastian and the Chrome Web Store Team,

Our product, a Chrome Extension (bcocdbombenodlegijagbhdjbifpiijp), used by 600.000 people on the platform, has hit a critical problem caused by an incompatibility with the recent Chromium browser API. We patched and submitted a fix v38.0.7 almost immediately, however it is in review for the past 7 days. All this time we are loosing customers.

We are getting bombarded by support tickets, angry reviews, negative ratings, refund requests and chargeback. This directly affects our revenue and incurs business losses. We can not wait another day, nor 20 days. Please expedite the version review.

Please consider the following going forward:

1. Prioritize reviews proportionally to affected userbase.
2. Add subscription / paid model for faster review times.

Please do not hesitate to reach out to us directly.

Kind regards,

Hanna Laas @ INSSIST.com

[TK Tech]

I am enthusiastically offering my rallying vote and support for the ideas already suggested that long-established extensions with long history and/or large user bases get priority. 

As has already been mentioned, bug fixes can't be scheduled in advance by definition, so users have to sit for days or weeks, frustrated, confused, and angry, which gets directed toward us the developers for bugs that aren't getting fixed because our patched extensions are not being reviewed and published.

This is causing harm to so many developers, and I sincerely hope that the two suggested ideas are implemented as soon as possible. In the meantime, you offer a priority pathway to devs who need expedited reviews. 
The problem of new extensions being submitted is only going to grow exponentially with vibe/agentic coding tools available, so for obvious reasons, new extensions should definitely not be receiving the same attention as established extensions. 

Thank you for responding and for working on a solution (just hoping it's implemented fast). And if there's a short-term solution, why build a better long-term solution, that is certainly welcome as well. 

[Jack]

This situation really makes me wonder what legal rights we actually have as a Developer on the Chrome Web Store (if any).

I feel very weak right now, like there's nothing I can do to help my users. Sorry to be the guy complaining on here but this is currently where all my stress and anxiety is pointed towards as someone who is very focused on moving towards the next step in my business.

[Jack]

What happened to this?  Now that the problem actually is occurring for all of us..

[Jack]

While I'll always remain loyal to the Chrome Web Store even during stressful times like this, Chris over at Firefox has made a very good example of how developers should be treated. I reached out to them because I was having a delayed review, and he got back to me a day later saying this:

"Thank you for your message. I just forwarded your request to our review team, who will be taking care of that as soon as possible."

[Zhongbin Ning]

Extension: AutoGrok
Extension ID: nmgfpjbckmbhpndgpmkbgbmopnkigncc
Version: 0.0.26

Same situation, previous versions were reviewed within 24 hours, this is unusual.

And I have several other extension that were reviewed and updated very quickly over the last few days. However, there's one specific extension that hasn't been approved for many days now—even though it actually has more users than all the others.

I've contact developer support several times, but no one helps

[Sebastian Benz]

Hey everyone, thank you for your patience. I want to provide an update from the Chrome Web Store team. We're actively working to improve review times and have implemented different strategies to better prioritize extensions in our queue. We're already seeing an improvement in review times, but are still working through the queue.  I will provide another update when there is more to share. 

Please stay tuned and thank you for your (continued patience).

Sebastian on behalf of the Chrome Web Store team

[Jack]

Dear Sebastian,

Can you please clarify if the new implementations will take effect on existing pending reviewals (the ones we’re all waiting on) or only future ones?

[Sebastian Benz]

This should affect both, new and existing pending reviews.

[Resell Track]

Hi Sebastian,

Thank you for the update and for the work your team is doing to improve review times, it's appreciated.

I wanted to suggest a potential improvement that could really help developers: adding a way for us to see where our extension is in the review queue (or at least an estimated position or progress indicator). Having more visibility would make it much easier to plan and reduce uncertainty while waiting.

Thanks again for your efforts, and I look forward to future updates.

Best regards,
Thomas

[Oliver Dunk]

I wanted to suggest a potential improvement that could really help developers: adding a way for us to see where our extension is in the review queue (or at least an estimated position or progress indicator). Having more visibility would make it much easier to plan and reduce uncertainty while waiting.

We definitely appreciate the suggestions! Traditionally, we haven't shared much information along these lines. I personally think there's room for us to be a bit more transparent, but to set expectations, there is always a tradeoff. Even showing where an item is in the queue can give signals to bad actors about how long we are looking at their item and how the system works.

It's a really tricky problem, but the whole team is focused on bringing times back down again.

Oliver Dunk | DevRel, Chrome Extensions | https://developer.chrome.com/ | London, GB

--
You received this message because you are subscribed to the Google Groups "Chromium Extensions" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-extens...@chromium.org.

To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/chromium-extensions/c13c5c9e-946d-4cf7-be1e-94b3a8dcd020n%40chromium.org.

[Jack]

Since some extensions are still pending for over three weeks, I’m wondering how effective the recent changes have actually been — and whether review times are anywhere close to returning to how they were a few months ago.

Are there any estimated timeframes?

[Oliver Dunk]

We're definitely not back to where we were a few months ago - the issues are ongoing.

No timeframe for when this will be resolved but it's something we are talking about and working on every day.

Oliver Dunk | DevRel, Chrome Extensions | https://developer.chrome.com/ | London, GB

[Jack]

Dear Oliver,

Since this question hasn’t been questioned or answered directly,

Are you guys able to provide assistance in expediting reviews through support for critical bugs right now, or are we only supposed to stay patient and wait in queue?

I have a cashback extension with nearly 300,000 users and my withdrawal functionality is completely broken due to a critical bug, as well as the extension being entirely broken for all new installs since the bug. (My submission does include new features as well)

If we have no choice but to wait, can you please be clear on that.

[Oliver Dunk]

If the bug is not in your previous version, you can use the version rollback feature. Otherwise, you will unfortunately need to wait for the update to be reviewed.

To be clear, we don't have a process for expediting reviews on request.

Oliver Dunk | DevRel, Chrome Extensions | https://developer.chrome.com/ | London, GB

[Don Schmitt]

I’d like to reiterate my support for offering a paid expedited review option. These delays can have real economic consequences, and it would be valuable to distinguish serious, production-critical extensions from fart-button extensions.

While this may not represent a significant revenue stream, it would provide a practical solution for developers whose businesses depend on the store.

There is precedent for this approach. The developer registration fee already serves as an economic gate without a primary profit motive. A similar mechanism could be leveraged to provide a clear, intentional signal that certain updates require more timely review

To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/chromium-extensions/CAOsQqBk_8RBDObtmmJT_GtvXiNpBwiO6WsYLW5Qw3UsEvno6Wg%40mail.gmail.com.

[Jack]

Dear everyone,

I tried my best to see what they could do to help, unfortunately we have no options other than to wait patiently.

We must wait. They are not expediting reviews for anyone, they are not manually reviewing for us no matter how critical it is. To be clear, they don’t have a way to expedite anyone or move anyone’s position in the queue according to Oliver.

While I am unsure what the Chrome Web Store team does on an average workday, it is quite embarrassing that this randomly happened and they weren’t prepared and working on this BEFORE the delays started occurring.

Chrome web store has been growing for years, then apparently submissions went up by >1000% on a Tuesday?

Firefox is saying the same thing right now, “too many submissions lately”.

We’re all going through the same stress right now, and thank you everyone for speaking out because multiple developers raising concern is what is gonna get the problem solved.

[Oliver Dunk]

You're completely right - this wasn't an overnight change. It happened gradually but over a fairly short period. Since I've seen a few people mention it feels like deprioritizing new extensions would help, I did also want to mention that this is not just from new extensions - we are seeing more submissions across the board.

Similar to you, we definitely appreciate everyone who has shared their feedback on this thread and please trust that we're continuing to work on this.

Oliver Dunk | DevRel, Chrome Extensions | https://developer.chrome.com/ | London, GB

[Jack]

I don’t think new or already published matters at all. There are presumably more people updating existing extensions everyday than new ones.

What we are recommending could be calculated by several things:
- Weekly user count
- Harmless code changes (e.g. Why does changing a class name require a full review?)
- Trust score raised overtime from approved submissions or ID verification (Tied to developer account and extension ID)
- An option on submit for 10K+ user extensions to opt in “e.g. This is a critical bug change” lying could result in losing the feature permanently. Explanation for reviewers required.

To put into perspective why an extension with more users should be reviewed before an extension with 72 users:

If the power, water, or electricity goes out in a city with a 300,000 population, and also in small town with 72 population, which needs to be prioritized

Imagine the anxiety in 300,000 people versus 72. It’s as if the world is ending. Everyone’s panicking.

While it may sound selfish to low user developers, the answer is unarguable because of the amount of people affected.

[Jack]

While ID verification should not be used as a way to “trust” anyone, it could be used as a way to know someone is serious and give a higher priority.

[Jack]

Another cool thing could be only updating certain files, instead of a whole new zip file of everything, allow us to have an editor on the dashboard and make changes to single files.

[Inssist App]

Yes, I completely agree. Extensions with 500,000 users and 100 users simply cannot be treated the same way from a severity standpoint. Besides, review times of even a few days are unacceptable, especially for critical bug fixes.

There is a procedure to roll back to a previous version. However, it does not work if your application state has been migrated forward between releases, as rolling back would cause an older version to work with a newer state, breaking the extension. Rolling back also does not work when the problem is caused by a new browser version incompatibility.

The Chrome Web Store One Stop Support page does not work either. You simply get no response beyond the default, or get a response post-factum once the review has already passed.

> Dear developer,
> Thank you for contacting us. One of our associates will be in touch with you shortly.
> Sincerely,

> Chrome Web Store Developer Support

The review process itself is flawed. For example, our critical bug fix was incorrectly rejected after 2 weeks of waiting (Red Potassium) because a reviewer misread the description and injected the word "free" into it (the word "free" does not appear in the description), then claimed the product is not free, rejecting it due to a fabricated discrepancy. Item description did not update between the releases, by the way.

To put this into perspective, we lost 12% of our subscription revenue due to a critical bug fix taking 2 weeks to approve, not accounting for refunds, chargebacks, negative ratings, and support costs.

[Jack]

I believe they’re aware of the problem, working on the problem, but that’s not enough. It needs to be fixed yesterday,

They’re clearly focusing on keeping reviews a streamlined automated process, so instead of helping individual developers through support, they’re working on the system for all of us.

Remember, the team working on the review system are not the ones losing customers and revenue, they go home to their warm beds while we stay up. So don’t expect the same level of frustration and urgency that this is happening with all due respect to the team.

From my analysis of this forum, the Chrome web store team cares about us. We matter to them.

Please, hurry up Chrome web store team!

[Jack]

Also Inssist, if it helps, you do have the word “free” in your extension description:

SAFE & FREE INSTAGRAM DESKTOP CLIENT

[Inssist App]

Yes, I'm aware of that, thank you. The violation however, explicitly pointed to the manifest.description, not the plugin Description. Review stated "... Post free Instagram stories, reels, photos from web...". The word free was added by the reviewed, who then claimed the app is not free and rejected the update.

Besides, posting is free in the app, and some features are paid, so the review is factually incorrect either way.

In any case, we dropped the word everywhere we could just in case. It is inconsequential. What's important is that we are back into the weeks-long review queue.

[Jack]

Reviewed within 7 days! Thanks team!

[Resell Track]

Hello, it has been over a week that several clients have been waiting because I cannot release my extension, as a major bug makes it unusable.

Do you have an estimated time of resolution for this issue? Thank you.

Have a nice day.

(ID: pbbbhbhcaiepibbalaoecnnkhemcmmdb)

Thomas

[Ivan Skorikov]

Hey guys! My extension has been in review since April 10, 2026. It was a minor update that simplified permissions and the store listing. Before that, it had already been in review since around March 30, but I resubmitted without waiting for the previous review, so it has been about a month in total.

Since then, I’ve made a lot of improvements and fixes, so I’m not sure whether I should keep waiting for the old version to be approved or cancel it and resubmit the latest version.I assume there’s some kind of prioritization system in place indeed, since I’ve seen many extensions submitted after mine already approved. I just want clarity on what to do, because the suggestion to do NOT resubmit an extension seems very confusing considering above statement.

Please help. Have a nice day, everybody!

(id: mnhjlocendmnofdfdoggnjcifneknibn)

[Oliver Dunk]

Since then, I’ve made a lot of improvements and fixes, so I’m not sure whether I should keep waiting for the old version to be approved or cancel it and resubmit the latest version.I assume there’s some kind of prioritization system in place indeed, since I’ve seen many extensions submitted after mine already approved. I just want clarity on what to do, because the suggestion to do NOT resubmit an extension seems very confusing considering above statement.

There isn't a prioritization system. Review is based on more factors than just submission time (some submissions will need more in-depth review), which is why your experience may differ from someone else's.

Since then, I’ve made a lot of improvements and fixes, so I’m not sure whether I should keep waiting for the old version to be approved or cancel it and resubmit the latest version.

It's ultimately up to you:

• If you just want either submission to go live, the fastest thing is to wait. Your existing submission will be moving through the queue.
• If you specifically want the latest version to go live as soon as possible, then cancelling may make sense. Otherwise, you have to wait for the current submission to be approved, and then make a new one.

Oliver Dunk | DevRel, Chrome Extensions | https://developer.chrome.com/ | London, GB

To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/chromium-extensions/6a973747-7dbd-4b23-b0b8-3f5f21effb88n%40chromium.org.

[Zhongbin Ning]

All I can say is that these guys are no help at all and just keep giving perfunctory replies.

I suspect that extensions pending review are simply slapped with a "waiting" label and thrown into an endlessly long queue. Why do I say this? As I mentioned in my previous reply, I have several extensions. The others get reviewed very quickly (I've actually released multiple versions of them during this timeframe), but this one specific extension hasn't been approved even after waiting for days.

What's really frustrating is that the extensions getting approved so quickly are mostly just new feature additions, whereas the version of the extension that is stuck waiting for review happens to be a bug fix that impacts all users.

[Ivan Skorikov]

Thanks Oliver! 

Really appreciate it!

[Prashant Singh]

Our extension is also in review since 11th April, its close to a month now. Not sure how will we keep up with rapid development and bug fixes if the review system is so much delayed. 

Extension id - ojplmecpdpgccookcobabopnaifgidhf

We have already made two extra version live on Edge and Firefox. Here stuck with old fixes.