Currently Being ModeratedNov 10, 2012 11:32 AM (in response to superclay)
sometimes when the push does work I experience that if you have set the notifcitations as alert with 'view in lock screen' on and 'badge notification' on, new email disappears after a while without having even opened it.....
has anyone had the same issue??
Currently Being ModeratedNov 12, 2012 3:21 PM (in response to superclay)
i called apple support today because i have lots of clients with iphones and they are all experiencing the same issue. i was actually told by the apple rep that this is not an apple issue and that the issue is actually with microsoft's exchange server. the support rep was very nice, but not very intelligent. she gave me a phone number for tech support at microsoft and wished me luck. once i hung up the phone, i had a good laugh for 10 minutes before calling microsoft. then i called a friend of mine who works at microsoft in the exchange development team. he said that he has heard of this issue but it isn't a microsoft problem and i wholeheartedly agree. he suggested jailbreaking all my clients iphones and recoding them until apple can get their activesync issue corrected. that is insanely extreme, but the best solution seems to be switching to 15 minute fetch instead of push until apple fixes the activesync problem.
Currently Being ModeratedNov 12, 2012 3:41 PM (in response to superclay)
Id have a hard time believing it to be a Microsoft issue if push works just fine on my ipad with the same ios 6.0.1 installed. But im also no software engineer so what do I know. I just want it resolved. I have a hard time shelling out money for new technology that doesn't work the way it is supposed to work.
Currently Being ModeratedNov 12, 2012 7:39 PM (in response to jouellet04)
That attitude by your friend at Microsoft is likely why this is not yet fixed. I'm sure that both apple and Microsoft are pointing the finger at each other. Perhaps it's an issue that they should work TOGETHER to fix instead of passing the buck.
Classic case of 2 companies bickering while the consumer in the middle is screwed. Now call your friend at Microsoft and tell him to call a colleague at apple and stop the nonsense and blame game. Both apple and Microsoft can help each other. After all it still impacts a Microsoft product.
Your friend needs to step up his game and ask his manager if he can liaison with apple to examine this issue in detail. Not just laugh it off.
Currently Being ModeratedNov 13, 2012 3:50 AM (in response to Caesarp)
Actually, this really does show the problem is with Apple, not Microsoft. If push works on multiple versions of Exchange on every Apple iOS platform except the iPhone 5, then the problem is CLEARLY on Apple's side of the fence and with this device only. It shows there is something clearly wrong with the way the iPhone 5 is running iOS 6.0.1 and handling push email. I am not trying to be smart, or get Microsoft off the hook, but this one clearly belongs to Apple.
Currently Being ModeratedNov 13, 2012 4:01 AM (in response to Shalomlej)
And of course the maddening issue is that it's not all people with that configuration. I have an iPhone 5 running 6.0.1 and push works fine regardless of area, lte, wifi, etc. I'm on Verizon. I typically see emails on the phone as fast as I get them in Outlook at work. We are running Exchange 2010.
Currently Being ModeratedNov 13, 2012 4:12 AM (in response to Michael Pardee)
Absolutely. I have been thinking about this problem since it began. There doesn't seem to be any consistency to it. I have deployed 3 phones with no problem, 1 does have the problem. The difference is that the one that does not work is a 32GB, and the 3 that do work are 16GB.
Could everyone whose phone does NOT work chime in how much storage it has? Perhaps the problem lies with phones that have more than 16GB of storage. Of course, that may not be the problem, but it might be helpful to gather that information.
Currently Being ModeratedNov 13, 2012 6:12 AM (in response to Shalomlej)
I was one of the early posters and expeirnece the issue from Day 1 of iOS6. I'm on an IP 4 (non-s) 32GB/AT&T, and the issue was more than just push. Fetch would not work eitehr.
I spent the better part of 3 weeks experimenting with different configurations, resets, re-boots and restores. The ONLY way I could get Exchange accounts to work is if I ran the phone WITHOUT icloud.
I firmly believe the issue has nothing to do with the IP5 hardware. Rather, the conflict in iOS6 presents itself when iCloud and Exchange are running at the same time.
Apple solved my iPhone 4 problem by exchanging my 18 month-old IP4 running iOS 6 with a brand-new IP4 running 5.1.1. The Genius Bar associate advised me to NOT update the OS until the issue was resolved.
So I've been happily running 5.1.1 with Exchange and iCloud running side by side with no issues.
I'm very happy Apple stepped-up and provided me a workable solution. However, I am disappointed that they would indicate that it is a Microsoft problem. The OS is the problem.
Currently Being ModeratedNov 13, 2012 6:49 AM (in response to superclay)
Well I have the 16gb and I also have the problem with the push email. Also I never setup the Icloud so I do not think it is a conflict with that as well.
Apple had me do a log for a couple hours so they can look further into this issue. They told me that they are looking at this thread and wanted to collect data so engineering can look into it. Hopefully they do find something and having it working properly.
Currently Being ModeratedNov 13, 2012 6:50 AM (in response to bfish1974)
Great to hear that they're actually researching it now. All my devices are the 64GB iPhones 5's (1 black and 1 white). I've never setup iCloud email, but I do have iCloud backup setup.
Currently Being ModeratedNov 13, 2012 7:52 AM (in response to Shalomlej)
Even if it is ultimately an Apple issue, obviously Microsoft knows more about Exchange than Apple, since it is Microsoft's product. So it would help if Apple and Microsoft worked together on this to determine precisely what the issue is with iPhone 5 and iOS 6.x and push/active synch.
I don't like to hear about Microsoft employees dismissing this and pointing at Apple or vice versa. Work together and resolve it already and stop the nonsense.
Currently Being ModeratedNov 13, 2012 1:11 PM (in response to superclay)
Just to throw my two cents in...
I'm with Sprint running on 3G data in my area and on an 32 GB iPhone 5 running 6.0.1. Usually after placing a call, I "push" exchange email ceases. In addition, attempting to "fetch" email through mail only displays "Connecting..." and will eventually time out. The only way to fix the problem is to toggle airplane mode or reboot the OS.
Interestingly enough, i also have problems sending iMessages during these episides. However, cellular data is fine through Safari and other applications. Here's hoping we get a fix with 6.1. I hate having to rely on timed fetch attempts to receive my email on my phone, but having an utterly useless Exchange functionality isn't much of a step up.
Currently Being ModeratedNov 13, 2012 2:55 PM (in response to Michael Pardee)
I've posted a few times on this thread and still baffled. After three different Verizon IP5/LTE/64GB phones, Exchange push fails on all of them, usually within 24 hours. Yet we've now got four AT&T IP5 users with LTE, different capacities, working just fine on same Exchange server now for days on end. I've gotten approval to go forward with a 2nd AT&T phone for me as a backup, but I'm still not convinced that I'll get the phone and have no issues, because I've seen AT&T IP5 users post the same problem here, although to a lesser degree than Verizon.
I will say that Apple has actually been very good with my case on the Verizon IP5 Exchange push problem. They've gathered data and they follow up with me regularly, even when there is nothing new to report. They'll just check in, which I appreciate.
More Like This
- Retrieving data ...
- This solved my question - 10 points
- This helped me - 5 points