Closed
Bug 794131
Opened 13 years ago
Closed 13 years ago
Add-On Builder is creating packages using a NON-Release version of the SDK
Categories
(addons.mozilla.org Graveyard :: Add-on Validation, defect)
addons.mozilla.org Graveyard
Add-on Validation
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: diegocr, Unassigned)
Details
User Agent: Mozilla/5.0 (Windows NT 6.1; rv:15.0) Gecko/20100101 Firefox/15.0.1
Build ID: 20120905151427
Steps to reproduce:
Just wanted to point out that the Add-On Builder is creating packages using a NON-Release version of the 1.10 SDK. Causing we AMO Editors to mistakenly reject add-ons by using a non-release version...
Updated•13 years ago
|
Status: UNCONFIRMED → NEW
Ever confirmed: true
After bug 784553 was re-fixed yesterday, I'm getting less warnings from the validator. Yesterday, I was getting 25 warnings, including one saying I'm using a future version of the SDK and then 24 more saying I was using non SDK interfaces.
Today, I'm only getting the 24 non SDK interface warnings, not the future version one.
https://github.com/mozilla/FlightDeck/pull/169 should fix this.
I must've missed a step in the not-really-documented "Update Builder" process, so the 1.10 submodule ended up pointing to somewhere on the SDK's master branch, not the 1.10 tag.
Comment 3•13 years ago
|
||
Wes, can you also push checksums for the version that the builder was using to the validator? We have a lot of add-ons built from it in the queue.
Comment 4•13 years ago
|
||
How many is a lot?
These people unfortunately need to go back to builder, re-build and re-submit. We apologize for the convenience.
Comment 5•13 years ago
|
||
I know that Diego rejected at least three already, and there are dozens of other Jetpack add-ons in the queues. I don't know how many of them are from the Builder, but it's probably a high percentage.
Updated•13 years ago
|
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
| Assignee | ||
Updated•10 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
•