Extension Pending Review for 8+ Days — Version 1.2.1 | Item ID: nldidalaibkmnjhkoajecahpkchpljmb

[Modassir Alam]

Hello everyone,

I'm reaching out because my Chrome extension has been stuck in "Pending Review" for over 8 days now and I'm not sure how to proceed.

Extension Details:
- Name: Fillix - You Chill, We Apply
- Item ID: nldidalaibkmnjhkoajecahpkchpljmb
- Version: 1.2.1
- Submitted: March 27, 2026
- Status: Pending Review (since 8+ days)
- Previous version was reviewed and published without any issues

This is an update to an already live extension - not a new submission. Version 1.2.1 includes bug fixes and minor improvements only. No new permissions were added.

What makes this particularly urgent is that we are a DPIIT-recognized Indian startup and I had publicly announced a launch date for this version to our user base and investors. The extended delay is now directly impacting our go-to-market and reputation.

I have already submitted a request via the One Stop Support form. I wanted to also post here as I've seen Google team members help developers in similar situations in this group.

Could anyone from the Chrome team or the community advise:
1. Is there a way to get a status update on the review?
2. Is 8+ days normal for a minor update with no new permissions?
3. Any steps I can take to help expedite this?

Thank you in advance. Any help is greatly appreciated.

- Alam
Founder & CTO, Fillix (fillix.in)

[Bartek]

Mine is pending review for 2 weeks now.

[Igor Volodin]

I'm trying to publish for the first time. I've been waiting for 7 days. My management is baffled.
id:  eeeihlimfbnbinfeacgmjhkfpcgljfbi

I have no idea what to do...

понедельник, 6 апреля 2026 г. в 14:49:42 UTC+5, Bartek:

[Jack Shaba]

Hi everyone,

We’re currently handling Chrome extension distribution and rollout (including enterprise deployments), and recently hit an issue where CRX installs via policy fail on newer Chrome versions — errors like ERROR_REMOVING_OLD_IMAGE_FILE and ERROR_SAVING_CATALOG. Rolling back to older versions resolves it.

It looks like something changed in how Chrome validates or manages extension files during updates. Has anyone identified the exact cause or a reliable fix?

We work quite a bit with extension deployment and growth, so if anyone else is dealing with similar rollout or install issues, feel free to connect — always open to exchanging insights or helping troubleshoot.

--
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/51861dc1-176d-49c1-8d1e-43b0d07d12f6n%40chromium.org.