291963 - Incompatible extension alert is no longer displayed since bug 286034 landed

Status: VERIFIED DUPLICATE of bug 291981

(Toolkit :: Add-ons Manager, defect)

Description

[Robert Strong (they/them - no direct email)]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b2) Gecko/20050426 Firefox/1.0+
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b2) Gecko/20050426 Firefox/1.0+

When installing an extension that is not compatible with the version of Firefox
(e.g. the version of Firefox does not fall between the extension's install.rdf's
minVersion and maxVersion) there is no longer an alert displayed to the user.

Reproducible: Always

Steps to Reproduce:




From the js console
RDFItemUpdater:checkForUpdates sending a request to server for:
https://addons.mozilla.org/update/VersionCheck.php?reqVersion=1&id={5DB6B72E-5C55-47a0-AB3B-945B4023E398}&version=0.1.0&maxAppVersion=0.10&appID={ec8030f7-c20a-464f-9b0e-13a3a9e97384}&appVersion=1.0&appOS=WINNT,
item = ({id:"{5DB6B72E-5C55-47a0-AB3B-945B4023E398}", version:"0.1.0",
installLocationKey:"app-profile", minAppVersion:"0.9", maxAppVersion:"0.10",
name:"Bug ID 252418 Testcase 1", xpiURL:"", iconURL:"", updateRDF:"", type:2})

and then

RDFItemUpdater:_parseV20UpdateInfo: No updates were found for:
{5DB6B72E-5C55-47a0-AB3B-945B4023E398}
If you are an Extension developer and were expecting there to be
updates, this could mean any number of things, since the RDF system
doesn't give up much in the way of information when the load fails.

Try checking that: 
 1. Your RDF File is correct - e.g. check that there is a top level
    RDF Resource with a URI urn:mozilla:extension:{GUID}, and that
    the <em:updates> listed all have matching GUIDs.

Comment 1

[Robert Strong (they/them - no direct email)]

Attachment: testcase

This is a testcase from another bug and the extension name / description are
for that bug so, please ignore them. The minVersion is 0.9 and the maxVersion
is 0.10

Comment 2

[Robert Strong (they/them - no direct email)]

*** This bug has been marked as a duplicate of 291981 ***