Submit for Review — Missing Required Information, but all starred fields are filled (only difference vs approved version is Mobile enabled)

Extensions
1

Hi, I’m trying to submit version 0.0.2 of my extension for review and I keep getting “You are missing some required information. Please go back to Local Test and fill the fields in Version Details marked with *.”

The problem: every field marked with * in Version Details is filled in. My previous version 0.0.1 was approved with the exact same Version Details (I compared them field by field — Name, Summary, Description, Author Name, General Category, Categories, Logo 100x100, Taskbar Icon 24x24, Discovery Image 300x200, 5 Screenshots 1024x768, Author Email, Support Email, Privacy Policy URL are all present; EULA URL is empty in both versions).

The only difference between 0.0.1 and 0.0.2 is that in 0.0.2 I enabled the Mobile extension type (with mobile path set to mobile.html). When I uncheck Mobile, the error disappears. When Mobile is checked, the error returns — but there is no visible empty starred field anywhere related to mobile.

I’ve already: re-saved every tab, refreshed, logged out/in, and verified my author email. The error persists.

Extension Client ID: s7606qpsfeowllexcp4o4lfbeira5b

Could you tell me which specific field the system considers missing when Mobile is enabled? Thanks.

2

Did you set/provide a (valid) privacy policy? One is required for mobile apps (usually when request ID sharing is enabled too)

And version 0.0.1 is released? Not pending release/in the queue?

You can only have one version in review (or pending release)

3

Thanks Barry.

Privacy policy: yes, camfree — Política de privacidad is live and valid.
Identity linking is set to No.

On the third point — 0.0.1 is APPROVED but not released (I’m intentionally
holding the release until my backend rate limiting is ready). Does an
approved-but-not-released version count as “pending release” and occupy the
single slot? If so, is moving 0.0.1 back to a test state the only way to free
the slot, or is there another option that doesn’t lose its approved status?

4

yes

Either release or leave and reenter the queue

I noted that here

5

Thanks a lot Barry, that explains it — 0.0.1 being approved-but-not-released was
occupying the slot the whole time.

For anyone finding this later: the error message is misleading. It says “you are
missing some required information, go back to Local Test and fill the fields in
Version Details marked with *”, which sends you hunting for an empty field that
doesn’t exist. It would be much clearer if it said the slot is already taken by
another version.

My plan: I’ll move 0.0.1 back to a test state to free the slot, then submit 0.0.2
(which adds the mobile view). I’m not planning to release yet, so losing 0.0.1’s
approved status isn’t a problem — 0.0.2 supersedes it anyway.

Thanks again for the quick answer.

6

can always update (files and settings of) 001 and save 002 for next release

since leaving the queue

7

Good to know for next time — I’d already submitted 0.0.2 by then, and it’s in
review now with everything in it. Thanks again for the help.