Testing persistent and restart features

When testing your extension, you may notice that some features reset themselves or stop working when you load an updated version or after you restart Firefox. For example, you may be using local storage and notice that previously saved data disappears when you reload your extension. Alternatively, you may want to test your extension across a Firefox restart but notice your extension doesn't remain loaded.

This article explains why you see these behaviors. It then shows you what to do to ensure that features persist when you reload your extension and how to set up to test restart behavior.

Before we look at how Firefox treats the extension you're testing; there are a couple of features of Firefox and extensions that you need to be aware of: the add-on ID and Firefox profiles.

What is an add-on ID?

The add-on ID is used to uniquely identify each extension and in turn that ID is used to link an extension to certain features of the WebExtension APIs. These features are:

  • storage.managed—identifies data as belonging to the extension by its add-on ID.
  • storage.sync—identifies data as belonging to the extension by its add-on ID.
  • identity.getRedirectURL—the redirect URL includes the extension's add-on ID.
  • Native messaging—the native app identifies extensions that can communicate with it by their add-on ID.
  • pkcs11—the PKCS #11 module identifies extensions that can communicate with it by their add-on ID.
  • runtime.onMessageExternal—an extension sends messages to another extension using its add-on ID as the address.
  • runtime.onConnectExternal—an extension requests a connection with an extension by the other extension's add-on ID.
  • browserAction—the saved position of the button is identified as belonging to the xtension based on its add-on ID.

An extension can be assigned an add-on ID using the manifest.json file "applications" key.

"applications": {
  "gecko": {
    "id": "addon@example.com"
    }
  }

If the extension doesn't have an add-on ID defined with the "applications" key, it gets an add-on ID through one of the following:

  • If the extension is submitted AMO and signed, it's given an ID when it's signed.
  • If the extension is loaded using Load Temporary Add-on in about:debugging it's assigned a temporary add-on ID.
    Example of a temporarily loaded extension showing its various IDs

You'll notice an additional ID in the image above, the Internal UUID. This is a unique identifier given to the extension on installation. It's used to define the storage location for resources included in the extension and identify an extension's data in window.localStorage or indexedDB. However, you don't need to know its value. Its use in window.localStorage or indexedDB is transparent and to access resources included in the extension you use runtime.getURL, which returns the path to the resources. And, because it's unique to each installation, it doesn't provide an ID that can be relied upon for other purposes.

What is a Firefox profile?

Data that defines how the user has configured Firefox, along with information generated as they browse the web such as history and cookies, is stored in a special folder, called a profile. In addition to cookies, the profile holds local storage and other profile related content.

Extension behavior in Firefox

When you develop an extension, assuming you've not defined an add-on ID using the "applications" key, the default behavior in Firefox is as follows:

  • when using the Load Temporary Add-on feature in about:debugging your extension is assigned a new add-on ID each time you load it.
  • when using web-ext, in addition to getting a new add-on ID each time you launch an extension it's also launched into a new profile.
  • when a temporarily loaded extension is unloaded, local storage, such as that used by storage.local, window.localStorage, and indexedDB, is removed.
  • when you stop Firefox, any temporarily loaded extensions are unloaded so aren't available when Firefox restarts. This includes extensions loaded with Load Temporary Add-on in about:debugging and web-ext.

The consequences of this behavior, when reloading an extension, is that:

  • any data in local or sync storage is lost.
  • any redirect URL becomes invalid.
  • the extension will no longer be able to communicate with native apps or a PKCS #11 module.
  • it will no longer be possible to send messages or create connections between extensions.
  • you cannot test how the extension will behave if Firefox is stopped and restarted.
  • browserAction positions are not carried over

What do I do to ensure I can test my extension?

To get your extension to behave like a signed extension during development testing, use the following techniques:

  • to make sure an extension can use add-on ID dependent features between reloads, such as local storage or native application communication:
    • set an add-on ID using the "applications" key in the extension's manifest.json.
    • when using web-ext, make sure you use the same profile.
  • to ensure you use the same profile for multiple tests of an extension when using web-ext:
    • optionally, use Profile Manager to create a new Firefox profile.
    • find the path to your new profile or the default Firefox profile by following the instructions in How do I find my profile?
    • add the Firefox profile path to the web-ext run command as follows:
      web-ext run --firefox-profile [A PATH TO A FIREFOX PROFILE] --keep-profile-changes
  • to preserve local storage when removing a temporary add-on (such as between browser restarts):
    • go to about:config and set extensions.webextensions.keepStorageOnUninstall to true.
  • to preserve access to window.localStorage or indexedDB data when removing a temporary add-on (such as between browser restarts):
    • go to about:config and set both extensions.webextensions.keepStorageOnUninstall and extensions.webextensions.keepUuidOnUninstall to true.
  • to test restart behavior:
    • set an add-on ID using the "applications" key in the extension's manifest.json.
    • install the Nightly or Developer editions of Firefox. Note: You can also use unbranded Beta and Release builds.
    • go to about:config and set xpinstall.signatures.required to false.
    • package your extension into a ZIP file using web-ext or by zipping it manually.
    • install your extension using Install Add-on From File in the Add-on manager (about:addons).
      Note: Remember you'll need to reload your extension each time you change it.
      Note: If you don't set the add-on ID, when you load the extension you get an error like this:

      Example of the message displayed when an add-on ID cannot be found for an extension

      with a matching error in the browser console.

      Example of the message displayed in the browser console when an add-on ID cannot be found for an extension

Document Tags and Contributors

Contributors to this page: tophf, Dietrich, freaktechnik, rebloor
Last updated by: tophf,