I submitted my extension ConvoExport to the Microsoft Edge Add-ons store, and the first package failed validation. The reason was not in the code at all. The zip contained two manifest.json files: one at the root, and one inside src/.

How it happened

My packaging script builds a staging directory, copies the src/ tree into it, and writes a derived manifest.json at the staging root. The src/ tree already contained a manifest.json (the source manifest the extension loads during development). The packager copied it along with everything else, then wrote a second manifest at the root. The resulting zip had 30 entries, two of them manifests.

Why my own checks missed it

The packaging self-check verified that a manifest.json existed at the package root, and that its fields were correct. It never checked that it was the only one. A check that asserts presence cannot catch a duplicate.

The fix

Two changes, both in the packager:

  1. Strip manifest.json out of the src/ tree when staging, so only the derived root manifest is packaged.
  2. Add a self-check that fails the build if more than one manifest.json exists anywhere in the package.

After the fix I re-packed both targets: Chrome 38,223 bytes and Firefox 38,303 bytes, 29 entries each, exactly one manifest.json at the root. The corrected package passed Edge validation and the submission went to In review.

The general lesson is boring and worth writing down: validate the package the way the store does, not the way your build does. My checks verified the source tree; the store verifies the zip. Anything the packager adds, moves, or duplicates between those two steps is invisible to source-level checks. A one-line assertion — "exactly one manifest.json in the archive" — would have caught this before the first submission.