Updating to 3.2os causes major echo issues with callers. Anyone esle experencing this too?

I have posted about this also. I am on my third Watch. I had an apple care guy call me and I made some test calls and shared the diagnostics with apple. I saw on a macrumors site that they put a 4th 3.2.2 beta update out on 4/24. Apparently only available to developers now and no concrete info about whether it addresses the echo issue. They are aware of the problem...how quickly a fix comes for this particular issue is anybody's guess.

The first Watch was not updated to 3.2 and did not have an echo issue (had a crashing/texting issue). Returned that, the second Watch had 3.2 update done in the store when we set it up. When I then reported the echo issue their response was to go get another Watch. The third Watch came with 3.2 on it out of the box and had the echo issue. I have been working with them ever since.

I am hopeful that they will have a fix for this soon. It is too bad that you can't restore an older update, I am stuck with the 3.2 until they come out with a new one. I am going to check in with the apple care guy and see if the information they took from my Watch was helpful. Unfortunately he has been reluctant to give me any kind of time frame for the next update.

I wouldn't update! Keep checking this site for info on it. There are other threads about it as well. Search "callers hear their voice echo if I take/make calls with Apple Watch"

i will post any info I have as I get it.

It is absolutely the 3.2 update. I purchased a watch and immediately updated it. I didn't even use it on 3.1. Horrible call quality. I exchanged that and held of on upgrading for several months because I was concerned it could be the update. Last night I updated because of an issue with fantastical. The echo is back. Great. Just great.

Just purchased the watch and updated. Now have the echo on the other caller's end as well.