jelmervdl / translatelocally-web-ext

TranslateLocally for the Browser is a web-extension that enables client side in-page translations for web browsers.
https://addons.mozilla.org/en-GB/firefox/addon/translatelocally-for-firefox/
Mozilla Public License 2.0
65 stars 3 forks source link

not possible to connect to native TranslateLocally application #53

Closed cadeyrn closed 1 year ago

cadeyrn commented 1 year ago

I can't select the locally installed TranslateLocally application within the add-on's settings. The option is greyed out:

Bildschirm­foto 2022-11-03 um 22 07 52

What I did:

  1. I installed the M1/M2 version from https://translatelocally.com/ on my MacBook Pro with M1 Pro and macOS 13.
  2. I started the application.
  3. I installed the webextension version 0.7.2 from https://addons.mozilla.org/en-US/firefox/addon/translatelocally-for-firefox/ in Firefox Nightly (108a1, 2022-11-03).
  4. I opened the add-on's settings on about:addons.

The browser console shows an error message that could be relevant:

ExtensionError: No such native application translatelocally

jelmervdl commented 1 year ago

Hi @cadeyrn,

Could you try downloading the latest TranslateLocally build from Github and do the steps with that one? I think its this build you'd need: https://github.com/XapaJIaMnu/translateLocally/releases/download/latest/translateLocally.macos-11.0.x86-64.dmg

What might have happened is that the extension id for TranslateLocally for Firefox recently changed because I had to republish it to make it public. I fixed that in TranslateLocally the desktop edition as well, but I'm not sure whether those changes made it all the way to the website.

cadeyrn commented 1 year ago

Unfortunately it does not work with this version either.

cadeyrn commented 1 year ago

@jelmervdl I did a few more tests, these are my results:

Conclusions:

jelmervdl commented 1 year ago

@cadeyrn Thank you for testing this!

I can now replicate this. It looks like as if that build for some reason doesn't write the manifest files. I don't know why, but I either suspect a sandboxing issue on macOS, or just a bug in the mac version of TranslateLocally. I'll have to look a bit deeper into it, but this is definitely a bug in TranslateLocally.

I'll close the issue here and follow up on it on the TranslateLocally repository.