Just a day after Microsoft offered workarounds for an iOS 6.1 Exchange syncing bug and said that it was working with Apple on a solution, Apple has announced on its support page (via ZDNet) that it has identified the problem and is working on a fix./article-new/2012/11/iphone_5_black_white-150x170.jpg?lossy)
Apple has identified a fix and will make it available in an upcoming software update. In the meantime, you can avoid this bug by not responding to an exception to a recurring event on your iOS device. If you do experience the symptoms described above, disable then reenable the Exchange calendar on your iOS device using the steps below.
Apple details its own workaround until that update is available, advising users to go to "Mail, Contacts, Calendars" under "Settings," selecting the Exchange account from the accounts list, turning the switch for "Calendars" off, waiting 10 seconds and then turning it back on.
The bug, which caused iOS 6.1 devices to continuously loop when syncing a recurring calendar meeting invitation to Microsoft Exchange, isn't the first bug to stem from the two-week old iOS 6.1. iPhone 4S users were affected by a bug that hampered 3G performance, although that was fixed with Apple's release of iOS 6.1.1 a couple of days ago. There is no timeframe for when the fix for the Exchange bug will be released.
Top Rated Comments
Is it not a valid concern?
It's absolutely nothing like 'Safari feels snappier'.
If someone has a jailbroken device and has the exchange bug they need to update to fix the bug - but if that means they lose the jailbreak, where do they stand?
Of course, he means with the update.
Not a single eyebrow has been raised in regards to iOS 6.1/6.1.1 acting any "different". No issues to report, apparently. No increase in traffic, no change in expected functionality, etc.
That being said, the admins have said that iOS has never really worked right, and that your should treat your calendar as read only when using iOS.
Example situation (verified yesterday):
1) User A creates a recurring event with Outlook, User B and User C are invited. They receive the event confirmation and accept. User A receives acknowledgement of the acceptance from both users.
2) User A later remembers an important detail and updates the recurring event with their iOS device.
3) User B and User C receive an invitation to a "new" recurring event. Similar to the original, but with the new details. This is saved to their calendar as a second event, right next to the first. They accept the event confirmation again.
4) User A receives the acceptance confirmations for the event, but still sees it as just event #1. User B and User C see event #1 and event #2.
Expected behavior:
iOS devices should update just event #1 (the original), and never create event #2.
What 'No WiFi' bug? Don't have a single problem with my wife's 4S...