Problem with publishing GoogleTranslate@google.com.xpi extension

Hello.
I’ve been using Firefox 60 for a long time, but decided to switch to Firefox 96 because of problems with sites. In Firefox 60 I was using GoogleTranslate@google.com.xpi extension version 2.0.9, which I repacked from Chrome extension, so it is unsigned. But in Firefox 60 it worked with the setting xpinstall.signatures.required=false. In Firefox 96 this setting doesn’t work, Firefox refuses to install the extension. I tried to download Unbranded build of Firefox, but it turns out it is not available for Linux x86 (only Linux x64). Then I registered on AMO and tried to upload the extension. At first the response was that the manifest didn’t have an author listed. I specified. Then there was an error during validation:
Your JSON is not valid
Unexpected string in JSON at position 17
manifest.json
Please help me to understand what’s wrong. New users are not allowed to attach files, so I uploaded this addon to mega.nz
https://mega.nz/file/IN83DQ7K#bAU3T7OCLcRCDgKpdQf0BTmf3QgNOE3dByWPIOr4zH4

I am using Xubuntu 16.04 i386 and the last Firefox that the distribution’s developer (Canonical) built was version Firefox 88. So I use Firefox from Mozilla website. Also, I would like to make this particular extension work and not its analogs.

This extension seems to work fine and doesn’t load CPU core in background, like old extension and google translate site. I think I’ll stick with this new extension. But I’m still interested in publishing to AMO. Since I may also need an alpha version of the unsigned VkOpt extension.

The problem is in https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/manifest.json/author

I added a comma in the author section and now error:
Your JSON is not valid.
Unexpected token , in JSON at position 53
manifest.json
Well, I’ll go back to Firefox 60. I don’t like new Firefox and where software world is going.

It would’ve been helpful if you’d posted what your “author” field now looks like.

In the version from your first post in this thread, the “author” field contains:

"author": "Denis" {
	"email": "changed.to.prevent.spam@protonmail.com"
},

According to the documentation I linked, the “author” field has to be a string.
(In Chrome, too! Where’d you get the idea that you can add your e-mail in curly braces after the author field?)
So this works:

"author": "Denis",

But then it doesn’t contain your e-mail address.

There are three things you can do about this:

1
Instead of the “author” field, use:


and put your e-mail address in “url”, like this:
"developer": {
	"name": "Denis",
	"url": "changed.to.prevent.spam@protonmail.com"
},

But that doesn’t work in all browsers, see the “Browser compatibility” section in the “developer” field documentation.

2
Use both “author” and " homepage_url":


But then you have to use a website URL, not an e-mail address.

3
Use your e-mail address as the add-on’s ID.
But then most people will never see it.

The simplest solution is to put everything in the author field:

"author": "Denis <changed.to.prevent.spam@protonmail.com>",

Probably you were running the Extended Support Release of Firefox 60. The ESR series honors that preference; the regular release ignores it. See: https://support.mozilla.org/kb/add-on-signing-in-firefox

hans_squared It doesn’t work anyway.

jscher2000 Yes, Firefox 60 ESR from the Mozilla website.

I read the article. And I assume that the Ubuntu build of Firefox is considered unbranded. Because in Ubuntu Firefox 78 (NOT ESR!) extensions.langpacks.signatures.required=false parameter works.

If anyone is interested, older distribution versions of Firefox can be downloaded here:
https://launchpad.net/ubuntu/xenial/+source/firefox > right links to Binary packages > https://launchpad.net/ubuntu/xenial/i386/firefox
Well, it looks like you can’t. Timeout error is always there now. Although https://launchpad.net/ubuntu/bionic/i386/firefox opens.
As I feared. Luckily, I did some backups.