1838611 - Native Messaging does not work in Firefox version 114.0.1

Status: RESOLVED DUPLICATE of bug 1837830

(WebExtensions :: Untriaged, defect)

Description

[Mark Newman]

Attachment: FirefoxNativeMessaging.png

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/114.0

Steps to reproduce:

Hi, we have a Firefox web extension that uses Native Messaging to communicate with a desktop app. This was working fine with previous versions of Firefox including V113.0.2.
This has stopped working in Firefox V114 which Mozilla released Friday 9th June 2023.

Extension URL: https://addons.mozilla.org/en-US/firefox/addon/paygateplugin-extension-for-ff/
Extension ID: {65893287-5E0F-4B50-ACCA-AB4B9593094E}
Internal UUID: 7d4bdb11-13d9-42bf-8044-4ad5630312cd
Manifest URL: moz-extension://7d4bdb11-13d9-42bf-8044-4ad5630312cd/manifest.json

I assume you can see the details of our web extensions content and background javascript pages from web extension zipped package that I uploaded on 22nd Sep 2021.

User agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/114.0

Our product running in the browser calls our desktop app via the web extension when the product needs to. E.g. Could be for accessing a smartcard or USB token.

The web extension hasn't changed for 2 years and the last change was only to remove a comment i.e. the extension has been stable for quite a while.

Actual results:

The communication between the web extension and the desktop app failed.
The attached file shows a screenshot from the Firefox debugger.
Error message says "Error: No such native application com.paygate.messaging"

The registry settings are correct as these haven't changed for years:
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Mozilla\NativeMessagingHosts\com.paygate.messaging

NB. For legacy reasons, the desktop app is a 32-bit app which is why the registry entry is under "WOW6432Node".

Expected results:

Web extension should have called the desktop app via native messaging.
Sorry but not sure what else to say here!

Something has been changed in the latest Firefox release since it was all working with Firefox V113.

Comment 1

[Robert Longson [:longsonr]]

If you use https://mozilla.github.io/mozregression/ to get an exact regression range that will likely be helpful.

Comment 2

[BugBot [:suhaib / :marco/ :calixte]]

The Bugbug bot thinks this bug should belong to the 'WebExtensions::Untriaged' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Comment 3

[Rob Wu [:robwu]]

Probably bug 1837830, already fixed on Nightly and Beta, with pending uplift request to 114 (if there is another dot release).