Apple has now acknowledged the bug in a new knowledge base article titled “iOS 6.1: Excess Exchange activity after accepting an exception to recurring calendar event” on its support website.

Apple has also said that they’ve found a fix for the bug and will include it in an upcoming software update. In the knowledge base article, Apple has described the problem as follows:

When you respond to an exception to a recurring calendar event with a Microsoft Exchange account on a device running iOS 6.1, the device may begin to generate excessive communication with Microsoft Exchange Server. You may notice increased network activity or reduced battery life on the iOS device. This extra network activity will be shown in the logs on Exchange Server and it may lead to the server blocking the iOS device. This can occur with iOS 6.1 and Microsoft Exchange 2010 SP1 or later, or Microsoft Exchange Online (Office365).

Apple has also proposed the following workaround to the problem until the fix for the issue is released:

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.

Go to Settings > Mail, Contacts, Calendars

Select the Exchange account from your Accounts list.

Turn the switch for Calendars to OFF.

Wait ten seconds.

Turn the switch for Calendars back to ON.

Microsoft has also published a support document offering workarounds for the bug.

A new iOS software update is not ideal for jailbreakers, but lets hope that Apple only fixes this exchange bug and the security flaw we reported earlier and not the evasi0n jailbreak.

Disclaimer

This website is not owned by, is not licensed by nor is a subsidiary of Apple Inc. iPhone is a trademark of Apple Inc. The content of this website is not supplied or reviewed by Apple Inc. All articles, images, logos and trademarks in this site are property of their respective owners. Please follow this link to read the complete disclaimer.