Avatar for Username

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

This thread was archived. Please ask a new question if you need help.

"Docutracks Signer" extension stopped working after firefox update (114.0)

  • 3 replies
  • 0 have this problem
  • 30 views
  • Last reply by TyDraniu

info9384
info9384
more options

Hello,

We own an extension Docutracks Signer (https://addons.mozilla.org/en-US/firefox/addon/docutracks-signer) that is used to message a windows app. After the 114.0 update it seems that the exe is never invoked to start. We tried going back to previous versions and it works fine. Moreover we also updated to 114.0.1 and the problem still exists. We dont know what kind of additional info we need to provide you with, however we kindly request to help us on fixing the issue.

Kind regards, Docutracks Dev Team

Hello, We own an extension Docutracks Signer (https://addons.mozilla.org/en-US/firefox/addon/docutracks-signer) that is used to message a windows app. After the 114.0 update it seems that the exe is never invoked to start. We tried going back to previous versions and it works fine. Moreover we also updated to 114.0.1 and the problem still exists. We dont know what kind of additional info we need to provide you with, however we kindly request to help us on fixing the issue. Kind regards, Docutracks Dev Team

All Replies (3)

TyDraniu
TyDraniu
  • Top 25 Contributor
more options

Is there any related error in the Browser Console (Ctrl + Shift + J)?

info9384
info9384 Question owner
more options

Thanks a lot for the immediate response.

The only error we are getting is "Error: Attempt to postMessage on disconnected port".

The problem though seems to be that the windows app that we try send message to, is no longer getting started by the browser. So, the above error looks as the result and not the cause of this misfunction.

Please let us know if you need any additional info. Kind regards

TyDraniu
TyDraniu
  • Top 25 Contributor
more options

As bug 1837830 has been fixed, please check the 114.0.2 version.