Well, that is sad but not surprising. Sloppy programming (I can only assume that this is the root cause of our problems here) can happen, it should be discovered in beta testing latest. However, bugs do pass sometimes, users got used to that. Customer service going into complete denial of this possibility is just dismal. Not a moment they consider that this really could be a fault on their part. I guess that's why people are not only talking of Apple fanboys (and gals) but rather of Apple disciples.
Of course it is the iTunes update that creates the fault. I didn't encounter it before, I encountered it for the first time with two devices right after updating iTunes. I updated both devices to the new iOS (thinking that may cure the problem) and still encountered the problem. I reverted to the previous version of iTunes and the problem was solved. Reverting to the old iTunes version did solve the problem for several other users as well.
While it is not impossible that something else is to blame I think there is pretty strong evidence suggesting that it is the update of iTunes that is to blame.
On answering this post I encountered two more examples:
When writing this answer I logged in (as you have to) and the site said that if I would trust this computer then I wouldn't have to verify with two-factor authentication again (I got the code on this same machine, so if anything it was a 1.1-factor authentication). When answering yesterday, I did say that I trusted this computer. It didn't help, I had to do this "safety" log-in thing again.
Second example: When the editor box appeared the site told me that there was an earlier version of this answer from 10 something p.m. yesterday. Well, your post, HaRooNeY, was certainly created much later than that. So, no, there wasn't any previous attempt to answer this post.