I searched the forum and I see a lot of questions related to this, but I still haven’t found anything that specifically answers my question.
I have previously installed add-ons that was working fine in versions before FF 43, and now with the new version they are disabled because they haven’t been signed and verified.
So, I did some research in how to sign an add on. I’m still confused by what I’ve been reading - is it possible for AMO to sign the previously uploaded add ons upon my request, OR do I need to upload a new version of my add ons?
If I need to submit a new version, what do I need to do differently? Do I need some kind of token? Where do I start?
I talked with Mozilla, and they told me to remove the “unpack” line from the install.rdf file. I did that, and submitted the new plugin.
They approved it, but the plugin does not work at all. It uses a sqlite dictionary for Chinese translation, and users are reporting they cannot load the dictionary. Before, they were able to load it when the unpack was set to true.
Now users are sending many emails about this.
Why was I instructed to remove or set unpack to false, when it broke the entire plugin?
What is the solution? I need an immediate solution ASAP. Things are getting desperate.
In the future we’d really appreciate if you kept it to one thread in one communication channel, instead of using different channels (email, discourse) as this makes it hard to keep track. In fact this could have been solved much earlier.
