I saw the same. Specifically, that the dropping words issue happens when the flag requiring on device recognition is set to true, but not when it is set to false. The fact that the behavior differs based on that flag feels pretty broken. But, having a mitigation for the word-dropping is nice too.

Well, I got a reply. It was this: Resolution: Investigation complete - Unable to diagnose with current information Recent Similar Reports: None It was a nonsense reply given how much detail and evidence I gave them for both reproducing and seeing the bug (watch the mp4 I sent you running your very own sample app - how hard is that?). And, I gave them other "recent similar reports" as well. Did they even read it? Based on that answer I doubt it.

Will those of us who file a bug see it updated when the issue is fixed or resolved?

It was in 17 as well. I first found it while building an app on 17.6. What changed in ios18 was that setting requiresOnDeviceRecognition to false stopped working as a workaround.

I and others reported the same behavior on a different forum. We see instances of it occurring on IOS17 (17.6.1 for me) as well. I have found that setting the run local flag to false seems to cause it to work correctly (no resets after brief pauses - I waited > 2 mins without seeing a reset), but I do not want to continue with that workaround as my app has a hard requirement to work while offline.