Experimental add-on install gives "Add-on not found" error

RESOLVED FIXED in 5.5

Status

defect
P3
normal
RESOLVED FIXED
10 years ago
3 years ago

People

(Reporter: arantius, Assigned: clouserw)

Tracking

unspecified
x86
Windows XP

Details

()

Reporter

Description

10 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.5) Gecko/20091102 Firefox/3.5.5 (.NET CLR 3.5.30729)
Build Identifier: 

For the extension at the URL given, I check "let me install this experimental add-on" then "Add to Firefox", and I get a 

"Firefox could not install the file at http://... because: Not a valid install package -207"

If I save the file, it is just an HTML page that says "Add-on not found!".

Reproducible: Always
Assignee

Comment 1

10 years ago
That link works for me.  This may have been a transient failure if the add-on wasn't sync'd to the mirror in time to show up or something.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → WORKSFORME
I still get:

Firefox could not install the file at 

https://addons.mozilla.org/en-US/firefox/downloads/file/69472/micro_menu-1.0.2-fx.xpi?confirmed

because: Invalid file hash (possible download corruption)
-261

when using Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1.5) Gecko/20091102 Firefox/3.5.5
Status: RESOLVED → UNCONFIRMED
Resolution: WORKSFORME → ---
Reporter

Comment 3

10 years ago
I am also still getting the same error as in my original post.

Start with -profilemanager, create a blank profile.  Navigate to above URL.  Check "let me install ...", click "add to firefox", -207 error.
I'm now getting the "Not a valid install" package; don't know what to do with this, but I'm confirming it, at least.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Assignee

Comment 5

10 years ago
I can confirm that file does not exist on disk.

$ ls
micro_menu-1.0.1-fx.xpi  micro_menu-1.0-fx.xpi

I'm not sure where it went, but I think the best course of action here is to add a new file to the existing version with the developer tools which should fix this problem.
Assignee: nobody → clouserw
Priority: -- → P3
Target Milestone: --- → 5.5
Reporter

Comment 6

10 years ago
Ok, the developer hub on AMO currently says, in 'versions and files' for this extension:

Version 1.0.2	No Test Results	1 In Sandbox file	November 10, 2009	Delete Version

It should probably say "0 files" if that's really the case.  I'll re-upload either way.
Assignee

Comment 7

10 years ago
(In reply to comment #6)
> Ok, the developer hub on AMO currently says, in 'versions and files' for this
> extension:
> 
> Version 1.0.2    No Test Results    1 In Sandbox file    November 10, 2009   
> Delete Version
> 
> It should probably say "0 files" if that's really the case.  I'll re-upload
> either way.

Yep, it's definitely in an inconsistent state - it thinks there is a file.  Deleting the file it think exists from the web interface and reuploading should fix it.
Assignee

Comment 8

10 years ago
(In reply to comment #6)
> It should probably say "0 files" if that's really the case.  I'll re-upload
> either way.

How did that go?
Reporter

Comment 9

10 years ago
Sorry I forgot to check back.  I tried once, and did the upload and delete steps out of order, probably deleting the one I just uploaded.  Tried again just now, and the last upload definitely took.
Status: NEW → RESOLVED
Last Resolved: 10 years ago10 years ago
Resolution: --- → WORKSFORME
Thanks, Anthony; verified.
Status: RESOLVED → VERIFIED

Comment 11

9 years ago
I'm also having this problem with my add-on: https://addons.mozilla.org/en-US/firefox/addon/103988 . Clicking this "Download" link on that page consistently gives an "Add-on not found" error page. I've tried deleting and re-uploading the file repeatedly, which hasn't worked.

Also, the add-on for which this was originally reported still doesn't work for me.
reopening based on comment#11
Status: VERIFIED → REOPENED
Resolution: WORKSFORME → ---
I get a Invalid file hash error -261 error while trying to install the add-on[103988]

Comment 14

9 years ago
As a workaround, downloading the latest version from the Version History page works. The bug is specific to "addon-*-latest.xpi" URLs. 

For example:
https://addons.mozilla.org/en-US/firefox/downloads/latest/103988/addon-103988-latest.xpi  -->  "Add-on not found!" page  -->  redirects to amo main page
https://addons.mozilla.org/en-US/firefox/downloads/file/89220/firesass_for_firebug-0.0.5-fx.xpi?confirmed  -->  installs the add-on

(Off-topic: A "not found" page shouldn't have a 200 status.)
Assignee

Comment 15

8 years ago
If someone has this problem, please don't reopen this bug - file a new one.

The backend has become much more reliable on python, so I'm calling this fixed.
Status: REOPENED → RESOLVED
Last Resolved: 10 years ago8 years ago
Resolution: --- → FIXED
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.