Q: Temp fix for iOS 6 not pushing Exchange mail

The KB article is not relevant. That assumes their push notification software is working, and something on the user's end is not set up correctly. That is not the case here - Apple has a bug to fix, and they need to fix it quickly.

I have stated before this is the third time in three releases Apple has broken push notifications.

I don't get it. Correct me if I'm wrong but if all Exchange ActiveSync users (including Gmail) with iPhones aren't able to get email reliably and consistently pushed to their devices, isn't that a huge problem? I imagine it would affect millions of people. Why is it then that the only coverage it has solicited is a single paragraph on Engadget and a few complaints here and there on help boards?

http://www.engadget.com/2012/10/01/early-ios-6-adopters-report-problems-getting- exchange-push-email/

Every time I get an email, I'd like the Mail badge to light up with a number so I know to check it. Back when I had a BlackBerry, it always worked. Are we certain there's nothing else that can be done to rectify this situation? I've wasted hours researching this: advanced Wi-Fi settings, etc., sending myself "test" emails. What's the deal here?

It's not "all Exchange ActiveSync users". It seems to be a complex condition of only iPhone 5 devices along with some set of circumstances that cause push to fail. It is a combination of events. Most of the people affected are on Verizon, but I am on AT&T and I see it, but I can go for a couple of days before it starts failing. Once it fails, you have to do something like reset settings or a reboot to get it working again.

Also, some people may not be receiving push notifications and don't even know it. You go into Mail and it will check manually and the mail shows up.

When the iOS push software is not broken, it's very reliable and works fine. But Apple has a way of re-introducing a  push notification bug in every major update. Later they fix it and everything works well.

I agree their QA is not great these days. It's sloppy. And when you're trying to break into the Enterprise and take BlackBerry business, it doesn't look good to the suits or the IT departments.

I received my att iphone 5 today.....same SH*T.  restored from icloud, erased sttings, restored as new phone,blah blah blah blah blah, icliud...blah blah blah  nothing has changed.  The only thing left for me to do to test this gigantic POS bug is to setup a new email account on my exchange srver and see if that works consistently.  otherwise I will be returning this and saying good bye to apple forever....

I feel your frustration - I've gone thru it a few times before with my iPhone 3 and 4 over a few OS updates. Push works great, get a new phone and/or update to a new iOS - then it's broken and you wait a couple months for a fix, then it's fine...until they (possibly) break it again later.

This bug is just not that hard to find. I can't believe in all their testing they couldn't have found it and fixed it in the iOS 6 GM.

They still need to learn a thing or two on how to develop reliable push.

Well the new account didn't work eithr.  Good bye Apple.

Frank, the Exchange issue with iOS 4 was patched just nine days after its release. It's already been two weeks since iOS 6 came out. Unacceptable is putting it mildly.

DOES ANYONE KNOW TIM COOKS EMAIL ADDRESS?

   Not a joke.  That is it

<Email Edited by Host>

I can only had that this probably has yet to explode because, as we've mentioned throughout this thread, this is a very specific problem with the iPhone 5 and iOS 6.  Folks in enterprise who updated their old devices--e.g., earlier iPhones and iPads--don't have much problems and think things are copacetic, which is great--until you get the 5. But currently the iPhone 5's demand is high with supply low.  So it has yet to permeate enterprise. I've got hundreds of people on the 4 and earlier.  We've only managed to get our hands on 6 new phones now because of limited supply--and the latest phones we got yesterday?  Yep, FAIL on enterprise Exchange Push. Enterprise Exchange is the gold standard in enterprise, so this is going to become big real fast. 

I find it amazing that the LTE/WiFi forum has less views and comments than this one, yet that was patched up within a week--probably because providers like Verizon forced people off unlimited data plans and realized the billing and PR nightmare this would cause for them.  So they probably raised cain with Apple.  Yet this problem?  Crickets.

I'm done with the 5.  I'm stopping the maddness and stopping folks from trying to upgrade to the 5.  Stick to your 4s (or, better, Blackberry phones).

He won't read your email. His army of admins will sift thru it. Not sure if he's already aware of this issue or if he cares. He's got bigger things to worry about, and there's a huge list of iOS bugs, some serious, some minor. He won't care about an email from regular users. Plus, he's got the very huge Maps debacle to deal with.

If you are the CEO or IT GM of a Fortune 500 company with thousands of iOS devices deployed in mission critical situations, maybe he'll listen to you.

All in all, this is a small blip for Apple.They've broken push before, some users make a stink, it hits the tech and IT blogs for a while, then they fix it and it's forgotten. Just another day at the office.

Sorry it sounds so callous, but that is the reality.

Well, I just sent him an email.

Hilarious.  Apple's moderator "host" removed the e-mail above within minutes.  That's got to be the FASTEST Apple response we've got so far .

It is public. Why would it be removed?   It is on the Internet here:

What is the mod concerned about?

<Link Edited by Host>

Well, I posted it on my blog www.churchnerd.org and encouraged others to spread the word.  My blog doesn't get that much exposure, but "hey" every little bit helps!  The squeekie wheel gets the most grease!

Too bad you have to be a squeekie wheel to get any response.

How funny is that?  No response from anyone that can/will help us - but the "moderator" edits out Tim's email address LOL.