iOS 11 breaks Exchange compatibility with new Exchange/365 setups
-
Apple, Microsoft Working to Fix iOS 11 Mail App Issues With Outlook.com, Office 365 & Exchange Accounts
Apple says it is working closely with Microsoft to fix an issue that prevents Outlook.com, Office 365, and Exchange 2016 account holders from sending...
Apparently this has been known about since one of the betas in April...
-
@e4tmyl33t Meh. Just Apple trying to encourage people to completely leave MS. As usual.
-
I for a moment actually thought Apple invented ActiveSync, but then I looked it up and no, naturally (because they're a software company that solves problems instead of just making things look pretty) they were using a Microsoft protocol.
-
Honestly, I'm not surprised at all by this. iOS and ActiveSync have had issues all the way back to iOS 5-6 where you couldn't properly interact with Exchange calendars. You'd try to update a meeting request or create a new meeting request and some people might get it, some people might not, some people might get 15 copies of it...
It's why my client company tells all their field users with iPads "If you have to make a meeting or make changes to a meeting, do it on your laptop, not the iPad!"
-
By iDiots, for iDiots.
-
I particularly like this:
Phil A.
1 day ago at 05:08 am
I could be wrong, but for me, it seems like more of an Apple problem than a Microsoft one: If it works in iOS 10 (and it does) and doesn't on iOS 11, then the logical conclusion is Apple have changed something in the way they implement the ActiveSync protocol that breaks thingsmattynat
1 day ago at 05:46 am
It was actually a Microsoft issue. I was the one working with Apple for my company on this for the past 2 weeks. Microsoft enabled HTTP/2 on their CAFE servers and that caused the issue. I guess its not compatible with iOS 11.So, iOS 11 not working properly with HTTP/2 is . . . . . Microsoft's fault.
-
That sounds like 'some from column A, some from column B'.
On the one hand, yeah, the server should be able to negotiate the version of HTTP, or degrade to the long-standing HTTP/1.1 if the client doesn't handle HTTP/2, or at the very least give a meaningful error message that says, "Whoops, this only works with HTTP/2, sorry". That's a
, but not the big one here.A brand-new version of iOS not supporting HTTP/2? Now that is a major
.
