Firefox Unbranded Build Downloads - gHacks Tech News

Firefox Unbranded Build Downloads

Unbranded Firefox versions are created specifically for developers to test their add-ons in without having to get development versions signed.

Mozilla introduced add-on signing some time ago and will make it a requirement without override in Stable and Beta starting with Firefox 48.

Firefox Stable and Beta versions cannot override add-on signing anymore which means that users cannot install unsigned add-ons in those browser versions. A switch was provided up until now to bypass this, but it will be removed with the release of Firefox 48.

Firefox ESR, Developer and Nightly editions ship with the override so that unsigned add-ons can be installed.

This posed a problem for add-on developers who wanted to test add-ons in development against Stable and Beta versions of Firefox. Simply speaking, with the restriction in place, they could not do so anymore without getting the development version signed first.

This however is not practicable for a number of reasons. First, any new version, and there are usually plenty during development, would have to be signed. Second, add-on signing adds to the development time.

Mozilla announced unbranded builds of Firefox some time ago to remedy that issue. Recently, very early builds were made available.

Firefox Unbranded Build Downloads

firefox unbranded build

The official Extension Signing page lists download links for unbranded Firefox builds.  Currently, only beta builds and development releases are available, but the first unbranded stable version of Firefox will be made available on August 2 when Firefox gets updated to version 48.

Unbranded Firefox builds are provided for all supported desktop operating systems. Mozilla suggests you create a new Firefox profile for those unbranded builds to avoid any complications.

Furthermore, a bug plagues these first builds that is rather annoying if you notice it too late. Basically, it can happen that these builds are updated to release builds of Firefox automatically.

To avoid this, Mozilla suggests that you disable the update functionality for the time being until the bug is resolved:

  1. Type about:config in the browser's address bar.
  2. Confirm you will be careful.
  3. Search for app.update.enabled.
  4. Double-click the preference.

Setting it to false prevents automatic updates. This does mean however that you need to download and install new unbranded versions of Firefox manually for the time being.

Also, unbranded builds show up as Nightly instead of Stable or Beta when you run them.

You do need to disable the add-on signing requirement in unbranded builds as well:

 

  • Type about:config in the browser's address bar.
  • Confirm you will be careful.
  • Search for xpinstall.signatures.required.
  • Double-click on the preference.

Setting the preference to false disables the add-on signing requirement.

 

Summary
Firefox Unbranded Build Downloads
Article Name
Firefox Unbranded Build Downloads
Description
Mozilla released so-called unbranded builds of Firefox Stable and Beta recently that allow users to disable the add-on signing requirement.
Author
Publisher
Ghacks Technology News
Logo

We need your help

Advertising revenue is falling fast across the Internet, and independently-run sites like Ghacks are hit hardest by it. The advertising model in its current form is coming to an end, and we have to find other ways to continue operating this site.

We are committed to keeping our content free and independent, which means no paywalls, no sponsored posts, no annoying ad formats (video ads) or subscription fees.

If you like our content, and would like to help, please consider making a contribution:

Comments

  1. Tony said on July 30, 2016 at 11:50 am
    Reply

    LOL… Hasn’t Mozilla repeatedly said that developers have had more than enough time to get ready for various changes?

    Yet, given the issues documented in this helpful article, Mozilla’s own developers apparently aren’t ready themselves…

    Oh, the hypocrisy!

    1. Joker said on July 31, 2016 at 8:34 am
      Reply

      Mozilla’s M.O.: Do as I say, not as I do.

    2. Mister Lurker said on August 4, 2016 at 7:04 pm
      Reply

      Clearly they are, and you just dislike the feature enough to try to reach for nonsensical arguments. They’ve automatically signed addons already on AMO, while doing all the other things they’ve done in the intervening time (releasing Firefox, and even shipping this build). Contrast that with addon devs who still haven’t even signed their addons. Yeah, Mozilla sure looks unfavorable in this comparison……

  2. Ben said on July 30, 2016 at 12:17 pm
    Reply

    What useragent does the unbranded browser send?

    1. Martin Brinkmann said on July 30, 2016 at 12:32 pm
      Reply

      Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:48.0) Gecko/20100101 Firefox/48.0

  3. yapadkoi said on July 30, 2016 at 12:24 pm
    Reply

    They also should create “unbranded versions” specifically for their users to test ads, telemetry and other similar (•̀o•́)ง in, they can using it without having to see this is Firefox doing this.

  4. Saibaba said on July 30, 2016 at 7:11 pm
    Reply

    Latest release (pending – Firefox 48) builds: Incoming Aug 2, 2016:
    https://wiki.mozilla.org/Add-ons/Extension_Signing#Unbranded_Builds

  5. vosie said on August 1, 2016 at 9:06 am
    Reply

    And what about Android? Where is the unbranded version for Android? Or will they keep the xpinstall.signatures.required pref available for the Android version of Firefox?

  6. Ken Saunders said on August 1, 2016 at 6:00 pm
    Reply

    Finally.
    After further exploration into it, I’ll probably end up using an unbranded build as my default for personal use (other builds for other things), and I suspect that others will too.

    The User Agent should be different. At least for statistical purposes.

  7. ams said on August 1, 2016 at 6:43 pm
    Reply

    (posted yesterday to ask this, but the comment never showed up)

    How would one self-build the unbranded version?
    Must you download sourcecode for stock firefox v48, then download “mozharness” from the FTP site linked to the wiki page regarding unbranded versions, then extract/overwrite contents of mozharness into the source tree?

  8. Baba Wanga said on August 1, 2016 at 11:49 pm
    Reply

    Python…

    # These packages are needed for mozharness unit tests.
    # Output from ‘pip freeze’; we may be able to use other versions of the below packages.
    Cython==0.14.1
    Fabric==1.6.0
    coverage==3.6
    distribute==0.6.35
    dulwich==0.8.7
    hg-git==0.4.0
    logilab-astng==0.24.2
    logilab-common==0.59.0
    mercurial==2.6.3
    mock==1.0.1
    nose==1.2.1
    ordereddict==1.1
    paramiko==1.10.0
    pycrypto==2.6
    pyflakes==0.6.1
    pylint==0.27.0
    simplejson==2.1.1
    unittest2==0.5.1
    virtualenv==1.5.1
    wsgiref==0.1.2
    urllib3==1.9.1
    google-api-python-client==1.3.1
    oauth2client==1.4.2

  9. WaterHack said on August 14, 2016 at 8:14 pm
    Reply

    @ams you got to compile, as the devs do with tinderbox: http://archive.mozilla.org/pub/firefox/tinderbox-builds/

Leave a Reply