The audio for this word is wrong. It's not "nyuso", but "hawayatenbea" indeed.
Still wrong audio (June 3, 2019).
Still wrong ... July 13th, 2019
Still wrong on March 30, 2020
Still wrong May 27, 2020
Still wrong as of June 11th, 2020
Not fixed 2020-02-23
Do mistakes actually get fixed in this Swahili class?
Still wrong audio (Jan 16, 2020)
Still wrong audio 19.03.2020 - reported.
So the audio says "hawajatembea," which from another comment means "they do not touch," and the text says "nyuso," which means "faces." They do not touch faces. Ninacheka.
Hawajatembea means they have not walked
Audio is way off
The voice sample does not match the answer
Pleased sort this out.
still wrong. very confusing
Wrong audio still
Still wrong audio (26 Feb 2020)
I hear the correct audio (I am doing Duolingo in Edge, I lost all audio in Chrome)
I am confused about this one
Still wrong !
The voice says hawajatembea.
Audio still wrong 11th March 2020
The sound says "hawayatenbea". The word boxes show kuta, umeme, fanguo, nyimbo and Nyuso. I'll report it. March 18, 2020.
30.03.2020 still not fixed
My answer is correct!!!
I write what the voice says and I am being told it is wring.....
Please amend your records.
I see several other complaints, but no fixing of the problem.
Would someone please amend this.
How do we proceed?
Still wrong and reported. 23.04.2020
This needs to be fixed. Today is 4/28/20. There are the same reports from last year. Why hasnt it been fixed. We can't put the correct answer in if it's wrong!
audio still not fixed MAY 4th 2020
Ok now that is a huge mistake, please so something about it!!!
24/ may /2020 audio still not fixed
They fixed the audi to match nyuso, it's no loud enough.
Audio is still wrong. Reported on June 25th 2020
As of July 1, 2020 not fixed yet! Maybe by 4th of July?
It won't be fixed until the release of the updated Swahili course: this may take a while, probably not before the end of this year (2020)!
an updated swahili course? where have you heard of it?
Still wrong June 2020
Audio still not fixed July 2020
It is now July 2020 and the error has not yet been resolved. Wow, now really