Error Uploading Salary Calculator Extension
Hi everyone,
I recently built a small Firefox extension for my website https://calcolo-stpendionetto.it https://calcolo-stpendionetto.it , which helps users calculate their net salary in Italy using updated IRPEF and INPS rates.
However, when I try to upload the extension to addons.mozilla.org addons.mozilla.org (AMO), I keep getting this error message: Signing is not possible due to an error with the manifest file
{
"manifest_version": 2,
"name": "Calcolo Stipendio Netto",
"version": "1.0",
"description": "Calculate your Italian net salary (IRPEF, INPS, regional tax) quickly.",
"icons": {
"48": "icons/icon48.png",
"128": "icons/icon128.png"
},
"browser_action": {
"default_popup": "popup.html"
},
"permissions": ["activeTab"]
} I also tried switching to manifest_version 3, but then Firefox gave a warning that some properties like browser_action are deprecated or not recognized.
Has anyone experienced the same issue when uploading finance or calculator-related extensions? Is there a new manifest format or signing rule I might be missing for Firefox extensions?
Any help or examples from working extensions would be greatly appreciated. Marien Klin
Toutes les réponses (4)
Hi
I recommend that you ask about this on the official add-ons forum at:
https://discourse.mozilla.org/c/add-ons/35/l/top?page=1
The team there should be able to help you.
Paul said
Hi I recommend that you ask about this on the official add-ons forum at: https://discourse.mozilla.org/c/add-ons/35/l/top?page=1 The team there should be able to help you.
Thank you so much.
No problem, the team there should be able to help.
Hi Marien,
Yes, I’ve seen this error a few times. It’s not related to salary or finance extensions at all. The main issue is that AMO no longer signs Manifest v2, even if the file looks valid. Switching to Manifest v3 and replacing deprecated fields like browser_action with action usually fixes the signing problem. Running the manifest through Mozilla’s validator before upload helps catch this early.
I faced similar validation quirks while working on small age calculation tools, which is why I now prefer offering calculators directly on the web instead of extensions.