Currently Being ModeratedSep 25, 2012 5:32 PM (in response to noahs)
I did not do a restore and honestly, I do not want to do a restore for a brand-new iPhone 5 I just got on Friday, which I did a restore from my iPhone 4 backup. It was working fine until today (although I have apsd crashes on the 23rd and 24th as well). I have found with these push failures, restore never solves it. It's always a bug Apple has to fix. These daemon processes are critical and should NOT be crashing. 3rd party app crashes you can excuse, but not Apple apps and especially critical daemons.
Currently Being ModeratedSep 25, 2012 5:34 PM (in response to noahs)
BTW, I am going to monitor the running processes (using SysMon and System) and if Push starts failing again, I'll see if there's a crash and if apsd is running. I bet it won't be.
Currently Being ModeratedSep 25, 2012 5:54 PM (in response to Frank Malloy)
Well, guess what? Push has stopped working again, but no apsd crash and the daemon is still listed as running. Still could be hung up.
Toggled Airplane Mode but it did not restart apsd (but it was still running tho)
What a mess.
Currently Being ModeratedSep 25, 2012 6:03 PM (in response to Frank Malloy)
Ugh. There's apparently a profile you can install that will give you detailed logging information on the apsd process. The logs didn't make much sense to me, but maybe you can understand them better. See here:
Currently Being ModeratedSep 25, 2012 7:59 PM (in response to superclay)
I'm having the same problem with iPhone 5/iOS6/Verizon. Had iPhone4S/iOS6/AT&T and had no issues with Exchange push. My friend just upgraded to iOS6 on his 4S and has had no issues either. Seems to be a bug related to the iP5 only.
Currently Being ModeratedSep 26, 2012 7:46 AM (in response to BeeJaay00)
I am also having issues with iPhone 5/iOS6/Verizon, as is another person I work with. We both had iPhone4S/iOS6/Verizon before with no exchange issues. I have 2 gmail accounts set up on my phne and get those emails automatically, but for exchange most of the time I have to manually update the mail client.
I updated my iPhone 5 via an iCloud backup, so none of my settings changed between devices.
Currently Being ModeratedSep 26, 2012 8:37 AM (in response to superclay)
Same issue for me. Push does not work reliably. Restarting the iPhone can make it work, but only briefly.
Apple Support Case: 353831711
My Apple support experience has been less than stellar...
Call #1: Placed on hold for 10 minutes before being disconnected.
Call #2: Escalated to senior support tech who promises to call me back.
Call #3: Never happens, since senior support tech does not call me back as promised.
Interesting side note: I get this problem on an iPhone 5, but not on a iPad 2 with iOS 6.
iPhone 5 / iOS 6 / Verizon & wi-fi does not work.
iPad 2 / iOS 6 / wi-fi does work.
Currently Being ModeratedSep 26, 2012 9:30 AM (in response to charles.mayer)
I'm expecting Apple Engineering to call me back tomorrow on this. Im just afraid that we will have to wait like 2 months for a fix on this instead of Apple providing us a patch, like they should right away. This issue can cost people money because they are not receiving timely emails. This issue not working is especially critical for business users. So far it seems to be happening mostly on Verizon iphone 5's.
Currently Being ModeratedSep 26, 2012 9:47 AM (in response to superclay)
I referenced dawho suggestions. All I did was turn off Safari sync in iCloud settings and my exchange mail is now pushing correctly. Will have to see how long this will hold up.
Currently Being ModeratedSep 26, 2012 9:53 AM (in response to David06812)
Probably not for long. That's one of the symptoms. You change a setting and it starts working then it crashes. This is what I see when the mobile push service fails on the phone:
Incident Identifier: 6E5AEBC6-E606-41AA-98A2-480023DAFDBC
CrashReporter Key: 78ef7a4ed36325aef9731e0532bf2536c3c051cd
Hardware Model: iPhone5,2
OS Version: iPhone OS 6.0 (10A405)
Kernel version: Darwin Kernel Version 13.0.0: Sun Aug 19 00:31:06 PDT 2012; root:xnu-2107.2.33~4/RELEASE_ARM_S5L8950X
Date: 2012-09-26 11:14:08 -0400
Exception Code: 0xdeaffeed
Reason: Power assertion timeout for "com.apple.message.fetchMobileSynchronously". Simply releasing it now.
Backtrace for power assertion: pid 434 (0x3b4e11d7 0x3b4e1697 0x37e27d05 0x122f0d 0x3b1c7ad4 0x3b11f28f 0x37e1fcd5 0x37e1fa13 0x394fca41 0x386f20e1 0x386f1fa8)
Thermal Level: 0
Thermal Sensors: 3343 3190 3217 3251 3347
Currently Being ModeratedSep 26, 2012 9:58 AM (in response to DQMIA)
Thanks for the info!
I hope this is reported to Apple. They have to have enough stack traces by now to find the problem. The question is how long is it going to take until they fix it.
With every major OS and hardware release I see this same problem pops up.
Currently Being ModeratedSep 26, 2012 10:14 AM (in response to Frank Malloy)
Yeah, I'm still waiting to hear back. They escalated my case yesterday and they told me I should hear something back today, but nothing yet. I'm going to call our Apple sales rep and see if he can push this up on the radar.
Currently Being ModeratedSep 26, 2012 10:37 AM (in response to superclay)
Does everyone that is having a problem on IO6 with an iPhone 5 also have a MacBook/ MAC that is on IOS6? I have noticed that my MacBook Pro gets some interesting iCloud messages in relation to Exchange and I was wondering if there was a correlation. I am going to try removing my email settings from my MacBook and iPad and then reset my iPhone 5 settings and see if that does the trick. I also had multiple crash logs from APSD and am experiencing issues with my exchange email and other push notifications.
Currently Being ModeratedSep 26, 2012 11:50 AM (in response to superclay)
yeah i just called apple having the same issues,and the service person ran me through a few things which didnt help. he replied that apple wasnt aware of this problem!
Currently Being ModeratedSep 26, 2012 11:54 AM (in response to shullshock)
Apple will always say they are unaware of any problem - whether you call on the phone, visit the Genius Bar, etc. It's not good business to say "Oh yeah, many people are having this problem. We're working on it and don't know when we'll have a fix".
They don't admit problems; they only offer advice in the form of "Reset, reboot, restore".
More Like This
- Retrieving data ...
- This solved my question - 10 points
- This helped me - 5 points