We don't believe the issues you are seeing are related to SmarterMail. We have seen, and continue to see, similar issues on Exchange as well as Office365 when using an iOS client. This last minor update for iOS has drastically increased the stability of the mail app in iOS and Apple has conceded that iOS 13 was extremely buggy upon release. As a result, they’ve vowed to make changes to their release processes for future updates.
Regarding responses from support relating to EAS, us “addressing (the issues) in some way” and our upcoming SmarterMail release, we have updated all protocols to be even more RFC compliant. We have also added new features for all protocols. I’m sure that’s what they mean, and not that we’re addressing this issue (these issues) in particular.) We have worked with Microsoft so that Outlook for iOS and Android perform similar to Exchange. We have also approached timezones differently, which will help calendaring. The number of improvements and changes we’ve made will improve things across all protocols and clients. That’s why we are asking customers to test the BETA to make sure anything they see today gets resolved early. If not, we want to know about it so we can work on it.
If your users are seeing problems using the mail app on iOS using EAS, it is critical they delete and re-add their accounts on iOS because the mail app doesn't recover well from a problem. Deleting and re-adding may help, but there’s no guarantee the issue won’t come back. It’s just that updates to the mail client and its ability to “recover” or stop repeating the same issues can be problematic at best — removing and re-adding can help things start fresh.
We are getting very close to the production release of the upcoming SmarterMail which will greatly simplify the conversation with customers because we will be focusing on one codebase... not two very different versions of SmarterMail.