Closed
Bug 656511
Opened 15 years ago
Closed 15 years ago
Read package name from install.rdf in upload XPI feature
Categories
(addons.mozilla.org Graveyard :: Add-on Builder, defect, P2)
addons.mozilla.org Graveyard
Add-on Builder
Tracking
(Not tracked)
RESOLVED
FIXED
Builder 0.9.6
People
(Reporter: krupa.mozbugs, Assigned: zalun)
References
()
Details
Attachments
(2 files)
steps to reproduce:
1. Log into AMO Builder and load https://builder.addons.mozilla.org/user/dashboard/
2. Click on 'Upload XPI'
3. Upload the attached jetpack
expected behavior:
Upload is successful. If upload is unsuccessful, user is shown a meaningful error message.
observed behavior:
Uploading an xpi return s a 403. Page says 'Wrong file'
[17:33:44.051] POST https://builder.addons.mozilla.org/addon/new/upload_xpi/ [HTTP/1.1 403 FORBIDDEN 3005ms]
| Reporter | ||
Comment 1•15 years ago
|
||
| Reporter | ||
Comment 2•15 years ago
|
||
screencast: http://screencast.com/t/0ZERHlkFH
| Assignee | ||
Comment 3•15 years ago
|
||
Thanks for the report - taking a look.
| Assignee | ||
Comment 4•15 years ago
|
||
The issue is that for uploading a XPI it has to be renamed as the field in package.json (the name field). In this case renaming "bobloblaw-1108.xpi" to "save-your-facebook-content.xpi" will solve the issue.
I consider this as a workaround. I've got already a solution for this and it's gonna be fixed in the next cycle of updates.
I am renaming the bug.
Assignee: nobody → zaloon
Priority: -- → P2
Summary: 403 while uploading xpis → Read package name from install.rdf in upload XPI feature
Target Milestone: --- → Builder 0.9.5
| Assignee | ||
Updated•15 years ago
|
Target Milestone: Builder 0.9.5 → Builder 0.9.6
| Assignee | ||
Comment 5•15 years ago
|
||
It is possible we will have to remove the entire feature.
Comment 6•15 years ago
|
||
Can you elaborate on this new commen, what changed? I ask only because your last comment seemed much more optimistic :)
| Assignee | ||
Comment 7•15 years ago
|
||
As David said on the meeting last time - it's a decompiler.
We will probably not know the exact hierarchy within the XPI and it might and will change to be more complicated to extract the exact packages which were used to create the XPI.
It might change to import a zipped directory of packages with hierarchy written in package.json files.
Comment 8•15 years ago
|
||
Given that, I would pull the feature for now, just remove it from the view.
| Assignee | ||
Comment 9•15 years ago
|
||
Upload XPI feature removed from sight
https://github.com/zalun/FlightDeck/commit/c11649df74ffa68cdf0d2f5675c8c74ec40160bb
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Updated•11 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.
Description
•