Yellow Magnesium: Functionality not working

The fix: rejected → fixed

  "action": {-Removed:     "default_popup": "Popup.html",+Added:     "default_popup": "popup.html",    "default_icon": {-Removed:       "128": "Icons/Icon128.png"+Added:       "128": "icons/icon128.png"    }  },

Paths now match the files on disk letter for letter. Then test the uploaded zip itself. Your working folder doesn't count.

Why you got Yellow Magnesium

• File-name case mismatch: the manifest says Icons/Icon128.png but the file is icons/icon128.png. That works on macOS and Windows but fails on a case-sensitive filesystem.
• The zip contains your source folder instead of the built output, or is missing the dist/ files.
• The main feature needs a login, and the reviewer had no test account.
• Your backend was down, rate-limited the reviewer or blocks their region.
• Errors fail silently, so the reviewer sees "nothing happens".

Pre-resubmit checklist

Your ticks are saved in this browser.

1. Unzip the exact file you uploaded into a new folder.
2. Load it via chrome://extensions → Developer mode → Load unpacked, in a fresh Chrome profile.
3. Use every feature described in your listing, and check the Errors button on the extensions page.
4. macOS and Windows hide letter-case mistakes. Compare each manifest path with the real file name character by character, or test on Linux.
5. Make every manifest path match the real file name exactly, including letter case.
6. If a login is needed, add a working test account and steps in the dashboard's test instructions.
7. Show a visible error message when your server fails, rather than doing nothing.
8. Bump the version and resubmit.

Common mistake: If you can't reproduce the failure, say so in the appeal and ask which feature failed. Reviewers sometimes test the listing's claims, not just whether it installs.

Appeal or resubmission note

Replace the [BRACKETS], then use the appeal link in your rejection email. Keep it short and factual, and list only changes you actually made.

Hello Chrome Web Store team,

My item [EXTENSION NAME] (ID: [ITEM ID]) was rejected with reference Yellow Magnesium.

I have reviewed the policy and made the following changes in version [NEW VERSION]:
- Fixed file paths that failed on case-sensitive systems: [FILES].
- Added test credentials and step-by-step instructions in the test instructions field.
- Verified the uploaded zip by loading it unpacked in a clean profile.

[ONE SENTENCE ON WHAT THE EXTENSION DOES AND WHY IT NEEDS WHAT REMAINS.]

I have resubmitted the updated package. If anything still does not comply, I would appreciate a pointer to the specific file or listing field so I can fix it.

Thank you,
[YOUR NAME]

Other fix guides

• Blue Argon Remotely hosted code (Manifest V3)
• Blue Zinc Prohibited products
• Yellow Zinc Missing or insufficient metadata
• Purple Potassium Excessive permissions
• Purple Lithium Privacy policy missing or incomplete
• Red Nickel Deceptive behavior
• Red Titanium Obfuscated code