I edited the Subject of the First Post and added this Short Summary.
Short summary 2020-01-20:
Issue: NoScript Updates Fail
Firefox users, on the NoScript BETA channel, when doing a 'Check for Updates'
either automatically or via "about:addons".
A 'new version' is Available but NoScript fails to Update.
The consensus includes:
* The 'NoScript you had', e.g. 11.0.12rc2, is still working.
* Firefox users will not gain any benefit from 11.0.13rc1. Either BETA 11.0.12rc2 or RELEASE 11.0.12
are the 'best versions', at this point in time, for Firefox users.
* It is possible to 'directly Install 11.0.12rc2' (see above).
* It is possible to Install 11.0.13rc1 in Waterfox Current (barbaz
or, if you 'bypass XPI signing checks in ESR', in Firefox 68.4.1esr (see above).
Cause: the XPI is not signed
Proposed fix: Upload a signed XPI (11.0.13rc2 - or higher)
Reflections after one week, in Question and Answer format
Q1. When was this noticed and reported?
Both garyf and DJ-Leith reported on 2020-01-13.
I posted because one of the things I can do, as a beta user, is give feedback.
For many years I've been on the beta NoScript (I don't automatically Update any Profile).
Q2. When was the cause discovered?
It took therube
less than two hours to post that the XPI was not signed.
Q3. How many people noticed?
Not many. The thread had about 300 views in the first week.
More than 5% were me as I updated the thread - I've deliberately NOT been opening it;
I've just checked the Main "InformAction Forums" page viewforum.php?f=3
to see if there were more posts and getit https://noscript.net/getit
to see if there is a new version.
Q4. Why so few?
The 'fail to Update' is 'almost silent' (see above - the 'blue dot' discussion).
I also don't know how many Firefox users are on beta NoScript channel.
Q5. Are you sure that NoScript is working OK?
To start with I was not. However, I am confident that 'all that has happened' is,
following a 'Check for Update' and finding a 'newer version', the 'updating process' failed
leaving the Profile with a working NoScript (the 'one you had'). This does illustrate that
the 'signing check' in Firefox will 'block the Install of the new XPI'; if it is not signed
(and you have not bypassed the signing check).
Q6. Why was an unsigned XPI uploaded?
I don't know, I imagine it was an accident. I imagine it is hard to develop for both
Firefox and Chromium at the same time (as well as Maintaining the Classic NoScript for the TOR Browser).
Another recent example (at the end of October 2019), where (I speculate) fixing a 'Chromium issue',
led to an unexpected issue, that I am aware of is:
11.0.5rc2 Endless SPAMMING requests to sync-messages.invalid