Siri dictation throws in extra words that I am not saying

I won’t be online much this week because of Thanksgiving. Catch hear something I’d like to get some feedback on from any of you. Catching it only works when it wants to, catchy but during a pause if I take a deep breath as if I’m frustrated or reluctant to say something and then start talking that seems to trigger some of these inserts. Catch up catcher catchy. Catching it seems to be working now but the words don’t get inserted until I start talking after the pause

Please understand this. I am not trying to figure out what the problem is or even what is causing it. I’m just trying to stumble on a way to make it happen at my command rather than randomly. Catchy Post at the end of that sentence took a few deep breath’s and lo and behold it threw in the word

c-a-t-c-h-y

I have been trying all day to post and update to everyone, but the POST button just puts me into a long wait with no response.

Maybe it is because it was such a long reply and it takes longer to get it all onto the forum.

I will keep trying and ask for help from apple. One way or the other, I will get a response posted along with a specific request for some help related to the response.

reporting back -- part 1

To all who have this dictation issue and follow this discussion. I have run into some "bumps in the road" that have made me very late reporting back. I thank you for your patience with this. In this post I will bring you up to date on progress so far. Then I will be posting follow-up action and details here ASAP.

Progress yesterday and today Wednesday):

The engineers responded to Crystal, our Apple Senior Advisor, with a list of steps each of us to take on our device. They propose this as a possible solution.

more parts to come

reporting back - part 2

Following this will be a post containing a copy or their response.

Updating to the latest IOS (13.2.3 released 11/18/2019) is the first step and an absolute pre-requisite. my iPhone is a 5s and is not in the list of devices compatible with iOS13. Crystal went through the rest of the steps with me just for my own education. When we tested the issue as the steps propose to do, it did not happen. That made me very happy until I tried again in an hour or so and it was happening again. After that I resumed my testing and found that the more I checked on it, the more it was happening. BUMMER! Then I tried to find a phone I could update to 13.2.2 and try it. 

OOPS when I tried posting this the system came back with:

You’ve exceeded the posting limits. Please try again in a few minutes

I will keep trying.

more parts to come . . . . . .

reporting back - part 3

Now I will ask anyone who is on iOS 13.2.3, or who can update to 13.2.3, please try go through the steps in the proposed solution and report your results back by replying to this post.

The fine print disclaimer at the bottom of this page says, "Apple can therefore provide no guarantee as to the efficacy of any proposed solutions on the community forums."  It is not about a guarantee, but simply about whether the proposed steps are really a solution after all. That's why we need to try it out and report the results back.

Now I will ask anyone who is on iOS 13.2.3, or who can update to 13.2.3, please try go through the steps in the proposed solution and report your results back by replying to this post.

The fine print disclaimer at the bottom of this page says, "Apple can therefore provide no guarantee as to the efficacy of any proposed solutions on the community forums."  It is not about a guarantee, but simply about whether the proposed steps are really a solution after all. That's why we need to try it out and report the results back.

OOOPS! posting limits again. I'll keep trying. That worked for part 2.

final part 4 to come . . . . . .

Hooray, part 3 worked

I have already composed my message to Crystal requesting our case to be re-opened based on your test results and also on the basis that iOS12 users, after using dictation without this issue before mid-October, have suddenly become unable to dictate what they need to.  As soon as I get some responses back from you folks, I will update the composed message and send it. The comes the fun part of trying to report on that.

Thanks again to all for your generous support by way of patience and cooperation.

Next post will be (part5) engineers propose solution steps

Stay tuned

You’ve exceeded the posting limits. Please try again in a few minutes.

yep! posting limits again. Continuing to try again every "few minutes"

After all this, I won't be surprised if they remove me from Support Communities entirely.

<< end of Part 4>>

Part 5 -- Yesterday's (Tuesday) call back documentation

Hello Bernard, 

The recommended steps are:

-Make sure iOS is up to date. If updating the device, test the issue after updating. 

-Make sure the Settings > General > Language & Region selections are appropriate for the customer

-Make sure the appropriate Settings > General > Dictionary languages are selected Uninstall any third party keyboards

-in Settings > General > Keyboard > Keyboards and test.

-Check for Settings > General > Keyboard > Text Replacement items related to the behavior the customer is experiencing Turn off each of the following one at a time

-in Settings > General > Keyboard and test after disabling each to see if the behavior is isolated to one of these features: Auto-Correction, Check Spelling, Shortcuts Predictive Make sure the customer has a current backup

-then use Settings > General > Reset > Reset Keyboard Dictionary and test the issue

Hope these are beneficial to all! Again have a great rest of your day and Happy Thanksgiving!

Crystal 

BadBernie inserting a comment here: (no, not the word CATCH) LOL

I just went through the steps on my iphone5s and ios12, and the issue went away.

I messed up where it says to turn items off under

Settings > General > Keyboard

When I got there they were all still ON !!!

Turned the correction one OFF , tested, and the issue was gone.