Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Add-ons: What does "signed.1-let-fixed update" mean?

  • 2 replies
  • 3 have this problem
  • 1 view
  • Last reply by Sun-flower

more options

All of a sudden my update add-ons list of Add-ons to update shows:

"signed.1-let-fixed update" or "1-let-fixed update"

after the Add-on names and version numbers that are available to update

I can't find any information on this when I Google it. I know what the "signed" means but not the "1-let-fixed".

Can anyone tell me what it means please?

All of a sudden my update add-ons list of Add-ons to update shows: "signed.1-let-fixed update" or "1-let-fixed update" after the Add-on names and version numbers that are available to update I can't find any information on this when I Google it. I know what the "signed" means but not the "1-let-fixed". Can anyone tell me what it means please?

Modified by Sun-flower

All Replies (2)

more options

Mozilla will begin requiring all extensions to be signed in order for them to be installable in Release and Beta versions of Firefox. Signing will be done through addons.mozilla.org (AMO) and will be mandatory for all extensions, regardless of where they are hosted.

more options

Thank you although, as mentioned in my question, I knew what the "signed" meant. It was the "1-let-fixed" part that I was questioning.

I have learned that, apparently, there was an issue with the "LET" programming command that affected some extensions. It seems that the add-on updates that had "1-let-fixed" added to them was showing that the author had fixed the issue.

Not that I understand any of that but that seems to be what it was about.