1038437 - AMO Add-on Compatibility Checker finds jpm-built extension compatible with fennec, incorrectly

Status: RESOLVED WONTFIX

(addons.mozilla.org Graveyard :: Compatibility Tools, defect)

Description

[Adrian Aichner [:anaran]]

User Agent: Mozilla/5.0 (Windows NT 5.1; rv:33.0) Gecko/20100101 Firefox/33.0 (Beta/Release)
Build ID: 20140714030201

Steps to reproduce:

I build an extension with jpm.

Extensions built with jpm are reported to be incompatible by Firefox for Android.

(addon-sdk-1.16)AichnerAd@Kuckuck:~/tmp/mozilla/JotFirefox/Jot$ cmd /c "%HOME%/tmp/mozilla/addon-sdk-1.16/bin/activate && jpm xpi -v -b c:/programme/nightly/firefox.exe"
Welcome to the Add-on SDK. For the docs, visit https://addons.mozilla.org/en-US/developers/docs/sdk/latest/
JPM info verbose set to true
JPM info binary set to c:/programme/nightly/firefox.exe
JPM info Running undefined on Jot
JPM info Creating XPI at  C:\Users\AichnerAd\tmp\mozilla\JotFirefox\Jot\jot.xpi
JPM info Successfully created xpi at C:\Users\AichnerAd\tmp\mozilla\JotFirefox\Jot\jot.xpi
(addon-sdk-1.16)AichnerAd@Kuckuck:~/tmp/mozilla/JotFirefox/Jot$ 



Actual results:

https://addons.mozilla.org/en-US/developers/addon/check-compatibility
reports
Validation Results
Tested for compatibility against: 	Firefox for Android 33.*
Compatibility Tests
0 errors, 0 warnings, 0 notices



Expected results:

I would expect an error stating the extension to be incompatible with Firefor for Android.

Comment 1

[Jorge Villalobos [:jorgev] (he/him)]

The compatibility validator only checks for a series of compatibility tests we use for desktop Firefox and Thunderbird. If we needed to do compatibility checks for Android we could add those tests, though. That validator doesn't do general tests like the ones you suggest, and I doubt we would add them.

Comment 2

[Adrian Aichner [:anaran]]

The UI suggests compatibility tests specifically for these:

<option value="1">Firefox</option>
<option value="18">Thunderbird</option>
<option value="61">Firefox for Android</option>
<option value="60">Mobile</option>
<option value="59">SeaMonkey</option>

At the very least the page should document what "a series of automated validation tests" actually means.