Definition issue on android app
This makes me believe that it is a recovering blunder, as I suspect ongoing words, which you've as of late really looked at the definition, are put away in the reserve, right
Thanks for reporting. We will look into it.
@zoran. This is the exact same bug we've been reporting for over a month now.
Yes, thanks. Our testers (and me) had problem reproducing the issue mentioned here, and then it's a problem for our developers to reproduce it too and figure out what's going on. We will find a solution soon. Thanks for your patience!
Thanks for working on this - would be great to see a fix. I'm still getting this regularly and it's pretty annoying.
Hi again everyone. Next time you encounter this issue, can you please take a screenshot of error console in your browser and send it over if you see any error there? That will help us figure out what exactly is going on and fix the issue. Thanks!
@zoran Is this what you mean? This is on Firefox, but note: this happens all the time on the ANDROID APP too. @Eleonora1337, the OP, posted about it being on the Android app and I mainly use the app too, where I get it many times per day.
Yes, it's like @nfera's screenshot, the first click nets no translation (or it just stays for a little time, so little that is unclickable) for the word, but if you close the definition tab and reenter, the translation reappears.
@zoran. If it helps, this usually only happens on words, which are either new or they are words which I haven't checked the definition in a long time. This makes me think that it is a retrieving error, as I think recent words, which you've recently checked the definition, are stored in the cache, right? Maybe it might have something to do with pereived Internet access?
Thanks, every information helps. We'll check that too.