@rick287: Thanks for posting that E-mail. It confirms what we (AppRiver and I) have been told by Apple as well. I agree....at this point it seems pretty obvious that this is an iOS bug and also how the bug is manifested based upon various users' setups.
Inevitably...some new person is going to find this thread and post something like: "The senior supervisor at my local Apple store confirmed that this is not a bug with iOS and that Google needs to update its servers to resolve the issue." Or "All you need to do is hard reset your device." And then the next person who comes along reads that as the last post and assumes that this was the final answer....and then instead of reporting the problem to Apple, they don't do anything or worse yet they do something that is a total waste of time and energy like hard resetting their device.
The fact that Mr. Jones confirms this is an iOS bug (i.e. Apple is no longer blaming everyone else on Earth for it) is encouraging, along with his prediction that there will be an update "soon." Well "soon" is a very subjective term. I suggest that if we want to make "soon" something that happens in the next 4-6 weeks instead of in the next 4-6 months....that it's a good idea for as many people as possible to report this individually. That will make it a "widespread impact" and a very high priority at Apple.
Also, I assume people in Apple Engineering have read and are monitoring this thread. That's what I would do if I were tasked with actually fixing the code to resolve this bug. Several users here have provided highly detailed information about how the bug is manifesting in their different setups which ultimately would be of major benefit to anyone who actually has to revise the iOS code. So I hope if anyone else has a totally different experience with this bug and has figured out either how to replicate it or better yet, identified exactly what causes it to show up in their technical environment, that's helpful.
Thank you for pursuing a tech support case with Apple and apparently getting somewhere with it!