Signing extensions created with Crossrider framework

Add-ons
1

I’ve uploaded an extension (for signing automated review) and it got redirected to a manual code check due to 133 warnings it produced.

The problem is that I need this extension to be working (able to install) in Firefox ASAP and getting redirected to manual-check queue on each update will terribly slow down my process.

None of these warnings accords to my code directly. All of them are related to Crossrider framework libraries (that I’ve used to build this ext) that are packaged into .xpi file. Is there a possibility you guys at Mozilla can anticipate this situation in furure and not redirect crossrider-based extensions to a manual check process?

During the upload process I’ve seen some information about using “known libraries” - is it possible that you consider Crossrider framework as a known library please?

2

I’m sorry, but we don’t allow add-ons built on the Crossrider framework on AMO because it hasn’t passed our review requirements. If you want your add-on listed on AMO, you’ll need to use something other than Crossrider.

3

I don’t want it listed on AMO. I just need it signed so end users are able to install it at all.

4

Problem is that Crossrider framework is not approved by AMO (yet). Without the approval, it wont pass review and without review it wont get singed.

Is it necessary to use the framework?

5

At the moment it is necessary to use Crossrider as we need cross browser support with the minimum cost (which by the way proved Crossrider not being the best choice for a simple ext like ours, we would be better off writing it for the browsers separately, but now it’s too late).

Not a happy ending I see here :-/

6

Would it help if I buy a signing certificate and deploy it via crossrider tool? (i.e. is it required that extensions are signed by Mozilla or maybe would it do if we sign it ourselves?)

7

Signing has to be done by AMO… it cant be done manually.
You can have an unlisted addon which has a slightly different review process.

Frankly, I never found the need for frameworks and/or libraries. None of the popular and complicated addons use frameworks.

8

At the point we started creating this extension the Crossrider seemed to be OK as Firefox did accept our extensions built with it, only with a warning. Now that we’ve finished building it the Firefox policy has changed and it refuses to install unsigned extensions.

Then we’ve started researching and discovered what was actual cause of that (Crossrider’s web panel doesn’t say anything about this issue).

We did apply to unlisted review process right from the start but didn’t pass it and we won’t be able to as the Crossrider’s built extension breaks AMO rules in number of ways. So the only option left is to re-write (luckily our ext isn’t complicated).

That said, if anyone is reading this, I strongly discourage using Crossrider framework in the hope of cutting some corners as Mozilla’s new policy won’t allow you to publish your work anyway :-/