Currently we only expose mozApps.mgmt to the home screen which is set as the current home screen. This unfortunately makes it so developers can not test privileged home screens in webIDE. For replaceable home screens to be usable, we need to expose this permission when installing a home screen over webIDE. This is currently where we check that the app is the current home screen: http://hg.mozilla.org/mozilla-central/annotate/32b0ce626ec8/dom/apps/Webapps.js#l269

Fabrice, Ted - do you guys have any ideas about how to solve this?

(In reply to Kevin Grandon :kgrandon from comment #1) > Fabrice, Ted - do you guys have any ideas about how to solve this? This is bound to the homescreen.manifestURL setting to match the new homescreen manifest url. That should happen by switching to the new homescreen from the settings app iirc.

Right, but when we test a home screen with the webIDE, it does not set the app as the default home screen. If a user installs an app using webIDE, they should be brought to a working app.

If so, the webapps actor should check the app role and switch the setting. Adding that at https://mxr.mozilla.org/mozilla-central/source/toolkit/devtools/server/actors/webapps.js#278 should work: if (aApp.role === "homescreen") { let settings = Cc["@mozilla.org/settingsService;1"].getService("nsISettingsService"); settings.createLock().set("homescreen.manifestURL", aApp.manifestURL, null); }

Switching the home screen of the developer phone doesn't seem like the right option to me either, but it might be a quick workaround. Seems to me we should probably either change the permission checking, or have some way of allowing it when being installed from a dev tool. Thanks for the info though, we could probably go with that initially.

Core Graveyard / DOM: Apps is inactive. Closing all bugs in this component.