Increase in junk translations since latest update

Since the most recent Android update (post-Beta), tapping on words brings up a lot more junk translations than before. For example, clicking on the word for “southerner” in my TL (Ukrainian) brings up the translation “that.” Similarly complex words are surfacing definitions like “and” or “at” instead of the actual definition.

A related problem is with contextual translations. Definitions for nearby words are popping up as the wrong definition for the word I click. This used to be a big problem a year or two ago (when AI translations were introduced) but went away for a while. Sad to see it back.

I’m having the same problem with Icelandic. The translations might be fine at the beginning of a lesson, but at some point they just get all scrambled up.

Yeah. I get some weird ones too. I also have a lesson where there’s several sentences in the middle are translated to spanish (instead of English) then goes back to normal

I remember not long ago that they introduced a bug that broke all the handling of hyphens, and after any hyphen, the AI put all its definitions on the wrong words.
Does this sound like that bug again, or something different?

Today my Arabic AI translations have become just the untranslated word in Arabic. I haven’t checked other languages yet today, but at least last night, they were still working properly.

Update: I checked with Turkish and Persian, both are unaffected. Only Arabic gives me this behavior; and only single words, phrases work normally.

I get sentences which lingq randomly refuses to translate; a few sentences later, everything works again. There’s nothing unusual I can see in these sentences (length and vocabulary are normal).

It happens on Android and on the laptop.

If I need to use Google translate for translation, I don’t really have a reason to keep paying for lingq!

I also observed this problem with Danish. Some sentence are translated correctly to German, and further on in the text it just repeats the Danish sentence. There doesn’t seem to be a rule for when this happens. I just hope that this bug will be fixed soon.

Thanks everyone, I appreciate your reports here. We will look into this and have it fixed.