This add-on is not available on your platform. This is not a public listing. You are only seeing it because of elevated permissions

I’m trying to publish a new extension with web-ext publish.

Everything seemed to have worked. I can see the extension when logged in as a dev and it lists a version + status “Approved”.

https://i.imgur.com/CeroRlw.png

However on the add-on page there are red warnings

  • This add-on is not available on your platform.
  • This is not a public listing. You are only seeing it because of elevated permissions.

When visiting the add-on page without being logged in. I get “Oops! We can’t find that page”

In similar thread i saw mentions of it’s not possible via web-ext publish, but that seems to have changed.

What else can I try?

Is “approved” the final status even though it seems to be automated approval in my case?

How can I double which visibility the web-ext publish is using? I saw that sometimes self-hosted is mentioned in other threads.

By default web-ext will publish a version as self-hosted. The first listed version has to be uploaded manually on AMO (you can obtain the file to upload with web-ext build). See also https://extensionworkshop.com/documentation/publish/submitting-an-add-on/ though the “new version” from on AMO will look slightly different (self-hosted will likely be pre-selected and you have to click a link to change it in the very first step).

Thank you, you are right! I’ll submit a new one and select “On this site.”

It’s my oversight not remembering that I’ve selected the other own “On my own” the first time.

Could be worth to add the selected listing (public <> own) somewhere after the extension was uploaded for the first time.

This is chosen per version that is uploaded.

Chosen per version, but the web-ext publishing can not set it.

So I’ll upload manual once with changing and the publish from web-ext?

Yes, and then you should be able to chose the distribution channel with web-ext, though note that you can not fill out certain information directly, like source code submission or release notes when using web-ext. See https://extensionworkshop.com/documentation/develop/web-ext-command-reference/#channel

1 Like