# Extension does not load via about:debugging

**URL:** <https://discourse.mozilla.org/t/extension-does-not-load-via-about-debugging/13582>\
**Category:** Development\
**Created:** [February 12, 2017, 7:11pm UTC](https://discourse.mozilla.org/t/extension-does-not-load-via-about-debugging/13582 "2017-02-12T19:11:17Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![nebulon](https://sea1.discourse-cdn.com/flex001/user_avatar/discourse.mozilla.org/nebulon/32/22232_2.png) [@nebulon](https://discourse.mozilla.org/u/nebulon)\
**Post date:** [February 12, 2017, 7:11pm UTC](https://discourse.mozilla.org/t/extension-does-not-load-via-about-debugging/13582/1 "2017-02-12T19:11:17Z")

</div>

Hi there,

I have a published extension and when I try to further develop this extension, I removed the published one from my browser, then I selected any file in the extension folder via the about:debugging page and the icon and name shows fine. However the extension is not actually loaded, the debugger shows no files loaded, nor does the icon in the toolbar appear.

The workaround for me was to change the [applications.gecko.id](http://applications.gecko.id) in the manifest.json, only then the extension gets loaded. So my question is, if this is a bug or if I am just not following the correct process to further work on a published extension.

Many thanks,  
Johannes

---

<div class="post-metadata">

**Author:** ![noitidart](https://avatars.discourse-cdn.com/v4/letter/n/9f8e36/32.png) [@noitidart](https://discourse.mozilla.org/u/noitidart)\
**Post date:** [February 13, 2017, 5:38am UTC](https://discourse.mozilla.org/t/extension-does-not-load-via-about-debugging/13582/2 "2017-02-13T05:38:51Z")

</div>

Thats weird, it works for me. I click on the manifest.json and it loads fine. Maybe if that doesnt work try zipping it up as an xpi, then selecting the XPI.

This really shouldn’t happen though, what version of Firefox are you on?

---

<div class="post-metadata">

**Author:** ![nebulon](https://sea1.discourse-cdn.com/flex001/user_avatar/discourse.mozilla.org/nebulon/32/22232_2.png) [@nebulon](https://discourse.mozilla.org/u/nebulon)\
**Post date:** [February 13, 2017, 9:49am UTC](https://discourse.mozilla.org/t/extension-does-not-load-via-about-debugging/13582/3 "2017-02-13T09:49:38Z")

</div>

Sorry for not mentioning, I am on Developer Edition 53.0a2 (2017-02-12)

I get the same behavior regardless of using the xpi, both about:debugging as well as install from file via the regular addons page. Is there any way I can get more extension loading debug logs?

---

<div class="post-metadata">

**Author:** ![NilkasG](https://avatars.discourse-cdn.com/v4/letter/n/0ea827/32.png) [@NilkasG](https://discourse.mozilla.org/u/NilkasG)\
**Post date:** [February 13, 2017, 12:28pm UTC](https://discourse.mozilla.org/t/extension-does-not-load-via-about-debugging/13582/4 "2017-02-13T12:28:16Z")

</div>

I have experienced the same thing. Disabling the release version, restarting Firefox, then loading the debug version works.

An other problem I ran into when I tried stuff like this is that if you debug an extension in one Firefox instance and then try to debug the extension in a second instance, the debugger will attach to the extension running in the first instance, obviously without telling you so. That can be very confusing.

---

<div class="post-metadata">

**Author:** ![noitidart](https://avatars.discourse-cdn.com/v4/letter/n/9f8e36/32.png) [@noitidart](https://discourse.mozilla.org/u/noitidart)\
**Post date:** [February 13, 2017, 2:55pm UTC](https://discourse.mozilla.org/t/extension-does-not-load-via-about-debugging/13582/5 "2017-02-13T14:55:03Z")

</div>

Man you’re a gold mine of knowledge! Haha awesome!

My experience agree with Nilkas’s experience - if I have loaded an addon with about:debugging multiple times, eventually things start to get real funky, especially when using native messaging. I have to “unisntall” it then restart the browser, then load again.