"Sorry No definition found" on all words.
Hello, I'm on Firefox 138.0.1 (64-bit) and the extension is 1.1.0. Not sure if there are any logs I could add. Please let me know if there's any information you need.
Same problem here. 138.0.1 (aarch64) on Windows
Latest version has fixed this issue. Sorry for the inconvenience caused.
cc @geminize77 @uninhm
I am using 1.2.0 on Zen browser 1.12.8b (Firefox 138.0.4) (64-bit) and still facing the "Sorry No definition found" error.
similar to https://github.com/meetDeveloper/Dictionary-Anywhere/issues/81
I’ve installed version 1.2.0 on Zen 1.13.2b (Firefox 139.0.4, 64-bit). It worked well for a day but has since stopped functioning, showing the message: “Sorry, no definition found.” I’ve tried reinstalling the extension, but that didn’t help. I’d appreciate it if you could take a look. Thanks!
I installed the latest version 2 days ago in Firefox (140.0.2 (64-bit)), and it has been showing this same error. I was hoping to use this extension because it was labeled as 'recommended' by Firefox. It would be greatly appreciated if you can please take a look and fix it. Thanks!
SNDF alert still in v1.2.0. Mac OS 12.7.6. Firefox 140.0.4
Latest version has fixed this issue. Sorry for the inconvenience caused.
extension version 1.2.0 with Firefox 142 (fedora) - not working and the experience is pretty much same since Firefox 138. Please fix. @meetDeveloper
Latest version has fixed this issue. Sorry for the inconvenience caused.
Thanks for the fix, it worked for a while and then I noticed it occurring again. On FF 142.0.1 (64-bit) and the extension is 1.2.0. TIA!
FF v142, Dict Any 1.2.0
I'm facing the same issue, since months. Every single word shows up "Sorry, no definition found". I use the latest version of the Add-on and latest version of Firefox as of today. I disabled all other add-ons. And I've just hit "Refresh Firefox" to fix this, but sadly no success. I'll really appreciate if the dev could look into this.
Im guessing the issue is related to fetching the definition from the 3rd party dictionary API
It seems that last time a similar issue occurred @meetDeveloper fixed the issue by removing credentials: 'omit' from background.js
It could be that the API now requires credentials or at least that its declared, so that would be the place I would investigate first, if I have time.
Also having this issue, unsure how to address