If you have an add-on built with a version of the SDK earlier than 1.14,
then it won't work with Firefox 22 (currently Firefox Aurora, and due to
release on June 25).
For it to work, it will need to be repacked with SDK 1.14.
There are three reasons for this:
* the SDK, in versions 1.12 and earlier, expects the platform's old
private-browsing APIs to exist and will fail to load add-ons if they
don't. This applies not only to add-ons that use private-browsing, but
to all add-ons. Until Firefox 22 a stub for these APIs is in place,
which is convincing enough for the SDK to work, unless add-ons actually
try to use prvate-browsing. In Firefox 22 the stub is removed.
* the __exposedProps__ change
) will break
everything earlier than 1.9
* add-ons that are built with 1.14 will automatically use the modules in
Firefox if they are running on Firefox 21 or higher. So once you are on
1.14, your add-on will automatically get newer versions of the SDK code
without having to repack. Of course, this doesn't mean we'll never break
compatibility again: things happen sometimes, and we have to change
APIs. But updates to add-ons to make them use a newer version of the SDK
code should not be needed any more.
We're working on a plan to repack as many add-ons as we can, and will
let you know as soon as we can whether we can repack your add-on for you