Beta version of an add-on uploaded on AMO but not visible

RESOLVED WORKSFORME

Status

addons.mozilla.org Graveyard
Developer Pages
RESOLVED WORKSFORME
7 years ago
2 years ago

People

(Reporter: Honza, Unassigned)

Tracking

Details

I have uploaded a beta version of Firebug addon (to start using the beta channel on AMO) but the file is not visible anywhere.

Here is where I expected the beta file to appear:
https://addons.mozilla.org/en-US/firefox/addon/1843/versions/

Name of the file I have uploaded is "firebug-1.6X.1b1.xpi"

Have I done anything wrong?

Honza
I don't see that version on https://addons.mozilla.org/en-US/developers/versions/1843/.
Any update on this?
I am still not able to upload the file (beta) and see it in the list of files here:
https://addons.mozilla.org/cs/developers/versions/1843/

Honza
One more question, there is a "X" letter in the file name 

"firebug-1.6X.1b1.xpi"

Do you think it could be the problem?

Honza
(In reply to comment #3)
> One more question, there is a "X" letter in the file name 
> 
> "firebug-1.6X.1b1.xpi"
> 
> Do you think it could be the problem?

What is the version number in the install.rdf?  This is what we look for:

define('BETA_VERSION_RE', '/(a|alpha|b|beta|pre|rc)\d*$/');

I can't look into this any further since I don't see your file in the developer pages.
The file is available here:
http://getfirebug.com/releases/firebug/1.6X/firebug-1.6X.1b1.xpi

Honza
I uploaded that file to allizom and it worked fine.

https://addons.allizom.org/en-US/firefox/addon/firebug/#beta-channel
https://addons.allizom.org/en-US/firefox/addon/firebug/versions/
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → FIXED
I have tried both addons.allizom and addons.mozilla and both sites work now, I did it exactly the same way as before so, I don't have any clue what was wrong before.

Thanks for your help!
Honza

Updated

7 years ago
Resolution: FIXED → WORKSFORME
(Assignee)

Updated

2 years ago
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.