Closed Bug 1136006 Opened 9 years ago Closed 9 years ago

SDK 1.17 sets "maxversion" to obsolete Firefox 30

Categories

(Add-on SDK Graveyard :: General, defect)

Product:
Add-on SDK Graveyard
Component:
General
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: nagle, Unassigned)

References

Details

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:35.0) Gecko/20100101 Firefox/35.0
Build ID: 20150122214805

Steps to reproduce:

Tried to load test version of newly built add-on built with latest SDK, 1.17, onto an Android phone running release Firefox 35.


Actual results:

Error message for add-on incompatible with this version of Firefox.


Expected results:

Should have loaded without complaint.

The .xpi file contains a cfx-generated "install.rdf" file with

        <em:minVersion>26.0</em:minVersion>
        <em:maxVersion>30.0</em:maxVersion>

so, of course Firefox 35 won't load the add-on.

See Bug 972931 for the previous time this had to be fixed in the SDK.
See Bug 893121 for the time before that...
See Bug 589936 for the first time, back in 2010, that this had to be fixed.
This can be reset on AMO, and when using cfx run/test this is ignored.  We aren't releasing a new version of cfx though, jpm is the replacement, https://blog.mozilla.org/addons/2015/02/26/jpm-replaces-cfx-for-firefox-38/
Blocks: cfx.py
Status: UNCONFIRMED → RESOLVED
Closed: 9 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.