Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
I’ve noticed today too that push is working properly on my push-supported IMAP account. Perhaps it is what I speculated; that it’s a server-side problem with the system used by Apple for push tokens.

Then again, I’ve had so many problems with Mail that I’m afraid I’m gaslighting myself into believing that the problems are fixed when it behaves as I expect. Only time or an acknowledgment of fault by Apple can tell for sure.
I have a feeling they will never acknowledge the bugs; this makes me weary about buying Apple products in the future despite being a big fan.
 
  • Like
Reactions: newellj
I suppose this is borderline funny, or maybe tragicomical. My 11 Pro Max, currently on 13.2, has had every manner of problem with Mail (and several other of the native apps, but Mail is a mission-critical task for this phone). It got so bad that I bought a used XS Max that still had 12.4.1 installed.

Possibly proving how incredibly inconsistent 13.x has been for me and many others, the 11 Pro Max is now downloading and alerting on Exchange emails exactly like the XS Max on 12.4.1 does. I don't know whether it got smarter from sitting next to the XS Max, or got scared that it was going to be sold, or what. ;) I'll be watching the two of them for a while. Nutty. What gives with 13? :(

Funny but my son, who has the 11 ProMax also said this morning his mail was working properly. Makes me wonder whether there is some ActiveSync issue with Microsoft servers and IOS 13. Or it is totally temporary and will stop working very soon.
 
I’ve noticed today too that push is working properly on my push-supported IMAP account. Perhaps it is what I speculated; that it’s a server-side problem with the system used by Apple for push tokens.

Then again, I’ve had so many problems with Mail that I’m afraid I’m gaslighting myself into believing that the problems are fixed when it behaves as I expect. Only time or an acknowledgment of fault by Apple can tell for sure.
I have a feeling they will never acknowledge the bugs; this makes me weary about buying Apple products in the future despite being a big fan.

I'd bet you're right about all three. On your second point, I'm trying to figure out how long I need to see this 11PM work before I'm willing to trust that it will properly deliver corporate email. The problem is that, as my 7th grade algebra teacher said, it takes every case to prove a proposition and only one case to disprove.
[automerge]1572619349[/automerge]
Funny but my son, who has the 11 ProMax also said this morning his mail was working properly. Makes me wonder whether there is some ActiveSync issue with Microsoft servers and IOS 13. Or it is totally temporary and will stop working very soon.

Interesting - another data point. Crazy stuff. It would actually be more believable, to me at least, that there were server problems than that they could take perfectly functional code in 12 and destroy its functionality in 13. I guess we wait and see.
 
  • Like
Reactions: thewhitehart
Maybe someone can help me understand - I don't understand the ins and outs of push but... A handful of users in our organization, who have and iPhone and upgraded to iOS 13.x (including the latest 13.2) have had nothing but problems with the default mail app, not a 3rd party mail app, and our on-premises Microsoft Exchange server (Exchange 2013). All iOS devices running iOS 12.x are fine but all devices running any iOS 13.x version have any and/or all of the issues that have been widely talked about. If we're talking about the default iOS Mail app and in-house Exchange server, how can any "server" side change that affects push tokens at Apple remedy the mail issues? The only way I can see that being a factor is if the iOS device talks to Apple in some way during the communication with in-house Exchange server, which I don't see happening... this would have to involve an update to the Mail app via an iOS update. Default Mail app and Exchange connections use ActiveSync, which hasn't been changed since December of 2018, so I would think that - YES - Apple fudged perfectly good code between iOS 12.x and 13.x.

I'm not trolling, just looking to understand where I might be ignorant. Thanks for any input!
 
  • Like
Reactions: drmorley
Maybe someone can help me understand - I don't understand the ins and outs of push but... A handful of users in our organization, who have and iPhone and upgraded to iOS 13.x (including the latest 13.2) have had nothing but problems with the default mail app, not a 3rd party mail app, and our on-premises Microsoft Exchange server (Exchange 2013). All iOS devices running iOS 12.x are fine but all devices running any iOS 13.x version have any and/or all of the issues that have been widely talked about. If we're talking about the default iOS Mail app and in-house Exchange server, how can any "server" side change that affects push tokens at Apple remedy the mail issues? The only way I can see that being a factor is if the iOS device talks to Apple in some way during the communication with in-house Exchange server, which I don't see happening... this would have to involve an update to the Mail app via an iOS update. Default Mail app and Exchange connections use ActiveSync, which hasn't been changed since December of 2018, so I would think that - YES - Apple fudged perfectly good code between iOS 12.x and 13.x.

I'm not trolling, just looking to understand where I might be ignorant. Thanks for any input!

I have no idea, really - the only thing I can really tell you is that I'm having exactly the problem you describe, and quite a few others here have this problem as well. If nothing has changed - if ActiveSync is the same, and iOS 13.2 is the same (obviously) - then I'm curious about why things seem to be normal today. I'm really not trying to argue about the cause, because I can't do anything more than make wild guesses.
 
If there's an intermediate service that deals with Apple Push Notification service that sits somehow between the iPhone and Exchange server, that might explain it. Perhaps the way tokens are requested/issued changed in IOS 13 and required an update at this intermediate service. Pure speculation and I don't really know how the mechanism works.

 
I have no idea, really - the only thing I can really tell you is that I'm having exactly the problem you describe, and quite a few others here have this problem as well. If nothing has changed - if ActiveSync is the same, and iOS 13.2 is the same (obviously) - then I'm curious about why things seem to be normal today. I'm really not trying to argue about the cause, because I can't do anything more than make wild guesses.

I don't take what you're saying as being argumentative at all - any more than I hope no one takes what I said/asked as argumentative either. Probably like everyone here, I would just love to get to the bottom of this and know it's resolved.
 
  • Like
Reactions: newellj
Well, it happened to me again, so I spoke too soon. I opened the app to one hour-old unread mail that didn’t appear in my inbox until I manually refreshed.

I don’t think they’re going to fix this anytime soon. They just don’t care. The complaints are mounting on Twitter, and they just don’t care. I filed a ticket weeks ago and had Apple Support call me several times. All of the solutions they offered were useless; they wouldn’t admit it’s a bug. So they’re not fixing it. It doesn’t exist as far as they’re concerned.
 
  • Like
Reactions: newellj
Well, it happened to me again, so I spoke too soon. I opened the app to one hour-old unread mail that didn’t appear in my inbox until I manually refreshed.

I don’t think they’re going to fix this anytime soon. They just don’t care. The complaints are mounting on Twitter, and they just don’t care. I filed a ticket weeks ago and had Apple Support call me several times. All of the solutions they offered were useless; they wouldn’t admit it’s a bug. So they’re not fixing it. It doesn’t exist as far as they’re concerned.

Watch Rene Ritchie/Vector's video, it was within the last week on iOS13 bugs. Basically unless it is critical they aint gonna fix it.

They MAY fix some Exchange issues if people make enough noise since those are corporate users (and the big companies have power to complain), but I dont see anything else getting fixed anytime soon in the mail app.

I've moved on to Outlook for the first time in a long time using a 3rd party app as my main mail solution.
 
  • Like
Reactions: thewhitehart
I notice that the mail app has a much easier time checking email on WiFi vs LTE, especially when there is an attachment.
 
I fixed all my issues.... by switching to my iPhone SE backup that I maintained on iOS 12.4.1. i forgot how nice it is to have notifications and push mail working again. I’ll just stay on this until they fix the issues. I don’t think it’ll get fixed until late 2019 or early 2020.
 
I fixed all my issues.... by switching to my iPhone SE backup that I maintained on iOS 12.4.1. i forgot how nice it is to have notifications and push mail working again. I’ll just stay on this until they fix the issues. I don’t think it’ll get fixed until late 2019 or early 2020.

Hell yeah, that's the fix. I had to buy the phone I traded in to get Mail to work - XS Max on 12.4.1. :mad:
 
I don't know if anyone notice (I haven't read whole thread) about iOS 13 Mail and macOS Mail too with new colour Flag system? If I flag email on iOS Mail on iPhone colour blue and it appear red on iPad Mail and Mac Mail. Flag colours don't seem sync. It doesn't matter where I flag email blue on any device it always appear red any other device.
 
Well, it happened to me again, so I spoke too soon. I opened the app to one hour-old unread mail that didn’t appear in my inbox until I manually refreshed.

I don’t think they’re going to fix this anytime soon. They just don’t care. The complaints are mounting on Twitter, and they just don’t care. I filed a ticket weeks ago and had Apple Support call me several times. All of the solutions they offered were useless; they wouldn’t admit it’s a bug. So they’re not fixing it. It doesn’t exist as far as they’re concerned.

But it is not only happening on Exchange, although that seems to be the most prevalent. I have one Exchange (O365) mail account and one iCloud. My Exchange consistently works as it should - lock screen notifications and also Notification Center previews and all. My iCloud account is the one that I often (but not always) have to open the native Mail app and pull down to refresh. IP11Pro, iOS 13.2.
I too have resorted to using the Outlook app for now. Much to be liked - appointment RSVPs etc. Two things missing though for me - 1) VIP and 2) the ability to start a draft, minimize it and then copy some text from another email, then maximize the draft and paste the text. VIP allows me to select a few people (like my boss, wife, etc) that would trigger a notification sound...... Lastly, native app means if I select a photo to email someone from the Photos app (for example) it would automatically select the native mail app.....
Please Apple, fix this mess. It is a critical problem, especially for business work....
 
  • Like
Reactions: thewhitehart
I can be in Mail and see everything in my combined InBox. Then 5 minutes later I'll get a new mail alert and when I go into Mail the InBox is completely empty and I need to wait for a refresh.

Here's a question. I've noticed along with others that it seems as though memory usuage has changed in iOS13 where apps restarting much more often when being selected after they've been in the background. Could Mail be also doing this (spontaneously quitting and then restarting maybe causing some of these refresh issues)?
 
Last edited:
  • Like
Reactions: tspear8183
I am experiencing all issues mentioned in this thread on a daily basis. I had zero issues in iOS 12 and regret upgrading to iOS 13 every time I use Mail. Email is my primary use case for my iPhone and without it I'm better off just carrying a laptop everywhere I go.
 
I can be in Mail and see everything in my combined InBox. Then 5 minutes later I'll get a new mail alert and when I go into Mail the InBox is completely empty and I need to wait for a refresh.

Here's a question. I've noticed along with others that it seems as though memory usuage has changed in iOS13 where apps restarting much more often when being selected after they've been in the background. Could Mail be also doing this (spontaneously quitting and then restarting maybe causing some of these refresh issues)?

My understanding is that IOS 13.2 caused most of the memory management/restart issues yet the mail problems have persisted through many IOS 13.X.X versions.
 
My understanding is that IOS 13.2 caused most of the memory management/restart issues yet the mail problems have persisted through many IOS 13.X.X versions.

Since 13.0 and before. However, as I noted and a few others also shared a few days ago, for some reason our Exchange mail now seems to be pushing, downloading and notifying correctly. Whether it stays that way, who knows; I'm not optimistic at this point.
 
The thing that drives me the most crazy is a persistent bug with the Mail app banner notifications since at least iOS11.

If banner notifications are turned on for Mail and you receive a bunch of them overnight, if you swipe to dismiss one of the banners, it sometimes causes them ALL to disappear from the lock screen/notification center at the same time. Sometimes it actually works correctly and leaves the remaining banners alone, but usually it doesn't.

I think a lot of people don't notice this one because a lot of people don't turn on banner notifications for mail and just use the red badge indicator (or they just assume that it's supposed to do that...):eek:
 
Every so often after an upgrade I check to see if mail works on ios 13. When it doesn’t I go back to Spark, which does (imap google mail).
 
My mail app constantly freezes. I’ve tried force quitting the app and restarting the phone but seems to be unusable for me.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.