v1.4.0 not working with Thunderbird 78

[friedpotat0]

v1.4.0 not working with Thunderbird 78

[popindavibe]

Thank you for the quick reply. I can confirm that Thunderbird 78 is not attempting to update to 1.4.0 anymore.

[friedPotat0]

Thank you for reporting. Sadly, the new version seems to be incompatible with the old Thunderbird 78. I have now marked the new version in the Thunderbird store that it will only work with Thunderbird 91.*. However, I don't know what effects this will have on the users' updates. I am trying to find a solution for Thunderbrid 78 as soon as possible.

[friedPotat0]

The add-on throws the following exception in the Experiments API on startup:

addons.xpi	WARN	Exception running bootstrap method startup on spamscores@czaenker: ReferenceError: WebExtensionPolicy is not defined(file:///.../src/experiments/experiments.js:3:19) JS Stack trace: @experiments.js:3:19
asyncLoadModule/module.asyncLoaded<@ExtensionCommon.jsm:1668:14

@dlh2 Do you have any idea what the problem could be? I can't find any useful information for WebExtensionPolicy on the web. I've already tried to add a condition to check whether WebExtensionPolicy is undefined and otherwise load the old ExtensionParent (see commit 7d90181), but Thunderbird 78 is still throwing the error. Thunderbird seems to check if the WebExtensionPolicy object is defined prior to the condition.

[dlh2]

Weird, try to debug it with CTRL + SHIFT + U/I

About the useful information, I don't really have any idea, as most of the ChromeUtils.Import are from xpCOM services, which are supposed to be removed https://developer.mozilla.org/en-US/docs/Mozilla/Firefox/Releases/57#changes_for_add-on_and_mozilla_developers as said in #38 (comment)

What I could understand WebExtensionPolicy was created at 2017-05-24 15:58, meanwhile the supposed XPCom Service was created at 2016-11-10 12:35

Therefore I think, on that day I just tried to search any solution on that part, so that's something we need to resolve as "WebExtensionPolicy" might not be indicated for that solution.

At the moment, my idea is to follow the guideline of MDN Extension.getURL() deprecated so we can use it with runtime, but for runtime we need to call it on background.js, so experiments.js can get it, therefore... We might have to ask the MDN developers itself

[friedPotat0]

I think the effort to continue supporting Thunderbird 78 is just too high. Only about 2% of the users of the add-on use a Thunderbird version older than 91.x. I'm really sorry to have to say this, but the support for the older Thunderbird versions will unfortunately be discontinued at this point. All users who still use Thunderbird 78 can continue to use version 1.3.1 of the add-on.