Closed
Bug 851874
Opened 13 years ago
Closed 12 years ago
Empty two-lined prefs.js file causes "Jetpack module version mismatch" warning in the validator
Categories
(addons.mozilla.org Graveyard :: Add-on Validation, defect)
addons.mozilla.org Graveyard
Add-on Validation
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 826408
People
(Reporter: cprcrack, Unassigned)
Details
Attachments
(1 file)
|
261.51 KB,
application/octet-stream
|
Details |
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.22 (KHTML, like Gecko) Chrome/25.0.1364.152 Safari/537.22
Steps to reproduce:
I created an xpi for my extension using the command "cfx xpi", and then I uploaded it to the Add-on Developer Center (which causes the validator to run on it), or just used the online validator to validate it. I attache the xpi you can use to incorrectly fire this warning.
Actual results:
The xpi was generated, but when you unzip it you realize there is an empty defaults/preferences/prefs.js file which only contains two empty lines. This causes the Add-on Validator to warn you when you upload the xpi with the following message:
Jetpack module version mismatch
Advertencia: A file in the Jetpack add-on does not match the SDK version specified in harness-options.json.
Module: defaults/preferences/prefs.js
Versions: 1.13.2/1.5-dev
defaults/preferences/prefs.js
Expected results:
The prefs.js should be completely empty (in that way the validator does not fire a warning) or the validator should be fixed to remove that incorrect warning when it reads a two-line empty prefs.js.
Component: General → Add-on Validation
Product: Add-on SDK → addons.mozilla.org
Updated•12 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 12 years ago
Resolution: --- → DUPLICATE
| 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
•