My guess is that the word probably hasn't gotten around yet that it is their problem and not a Google problem. My guess is that the tech that gave mshelbym the information about the fix talked to a supervisor who wasn't up on the issue at hand and has old information. I know that's annoying, but I also guess that they are working on a large number of issues in iOS, and they just haven't gotten out the current word on this issue.
I know we are all VERY annoyed with them on this particular issue, but they just recently accepted this as their problem and have told us the next release will fix it. I sure hope that's the truth.
It's bad that they can't get their support act together. They mislead people when they aren't communicating well. Based on the fact that there has been no response from Apple in this thread, I wonder if their support is under water.
We have reported here that iOS 8.1.3 is supposed to have the fix in it. We know that the problem is Apple's, and they have committed to fixing it. So, you can either be patient or switch platforms. However, be aware that ALL smart phone platforms have issues and you'd just be trading one set for another.
Yelling or getting annoyed at this point is just a waste of energy.
My wife tells me I am too fair, so if you don't agree with what I've written here, that's up to you. I'm going to be patient. I have been an Apple fan since 1986, when I was given a Mac Classic at my job. I have defended them throughout all this time, but I have also worked on Windows systems, Android and Blackberry (and Palm OS) phones, and I still prefer Apple to the others under most circumstances.
In addition, several people have been snarky with new posters on this thread. In their defense, the thread is now 35+ pages, and many people just won't read it from the beginning like I did several weeks ago. You can't change that. I can't change it either. Be nice, please? It won't get you anything if you are a dick to the other people looking for help.