1181388 - Include disabled simulators in runtime list (for signing)

Status: RESOLVED WONTFIX

(DevTools Graveyard :: WebIDE, defect)

Description

[J. Ryan Stinnett [:jryans] (Use needinfo, replies may be slow)]

Since we no longer actually use the JS code inside a simulator XPI, we could potentially let the current XPI fail the signing check, but still use the simulators from WebIDE's runtime list.

Definitely a hack, but potentially simpler than changing simulators to move the profile somewhere else, get them signed, etc.

Comment 1

[J. Ryan Stinnett [:jryans] (Use needinfo, replies may be slow)]

To test this, set "xpinstall.signatures.required" to true in about:config (and restart just to be sure).

Then, see if simulators can be started.  If not, we may be able to still show them by tweaking WebIDE's simulator list to include disabled ones.

Comment 2

[Jen Fong-Adwent [:ednapiranha]]

Attachment: Add-ons_Manager.png

Current behavior:

1. |xpinstall.signatures.required| is set to false, browser restarted.

2. Load WebIDE and installed a simulator (unstable 3.0)

3. Simulator is successfully installed, certified apps on the simulator load correctly.

4. |xpinstall.signatures.required| is set to true

5. Load WebIDE and install a simulator (unstable 3.0), browser restarted.

6. Tried to install a new simulator (unstable 2.2) but received this error in the console (which caused it to not install):
    addons.xpi	WARN	Download of https://ftp.mozilla.org/pub/mozilla.org/labs/fxos-simulator/2.2/mac64/fxos_2_2_simulator-mac64-latest.xpi failed: signature is required but missing

7. Checked about:addons and only see 3.0 installed but set as disabled (see attachment)

Comment 3

[J. Ryan Stinnett [:jryans] (Use needinfo, replies may be slow)]

Jen, thank you for doing this investigation, it was quite helpful!

Through work in bug 1190973 and bug 1191933, I was able to deploy signed simulators, so this is now no longer an issue.