I was hoping that you'd read a lighter tone with my "yuck" comment. I very much intended it to be a jokingly sincere comment, as Android is obviously not my preference and I try to temper calls to leave Apple's ecosystem. As it turns out, it does seem that I have inadvertently offended you with my comment, for which I do sincerely apologize. I certainly don't mean to come off as didactic to you or be a "boss" to anyone in this discussion, but I certainly am an authority on iOS matters, having been professionally trained by Apple at their headquarters in Cupertino. (I won't dig in further on this point, but I will point out it was Steve Jobs himself who was the marketing genius you referred to.)
On the point of not having "enough data to make the statement," I can safely say that I do have enough data to make this statement by virtue of the sheer lack of data about this issue. After scouring the internet and Apple's own internal service documents, this thread and one other post on an AT&T forum are the only places I've found any mention of a problem like this whatsoever. Even the dreaded autocorrect "I" issue, which became present in the recent 11.1 release, only affected a small percentage of users, but was still significant enough to find copious amounts of data on the topic almost immediately, including Apple's own support document about the problem. Our issue doesn't seem to have even a remotely similar magnitude.
Also, there is a guarantee that this is a software issue, by virtue of the fact that force-quitting the app resolves the problem temporarily, and all software issues can be resolved by doing a full restore and setup as new of the iOS device. Period. The point I was making is that this is not an ideal solution for most users, so we're looking for an alternative. If you feel so emboldened, put it to the test. Or take it to Apple and have them put it to the test. In my previous reply, I specifically mentioned that I did not discourage people from taking this issue to Apple. I was simply advising that we, as a community, could continue to troubleshoot together to find a less invasive solution for ourselves.
As for me, this will be my last post on this topic as I have no interest in further engaging your temper for what I thought was a collaborative effort. Reply if you must, but remember your audience will only be other users who are earnestly just looking for a solution for what I hope will only be a short-lived problem.
Thank you very much and have a nice day.