"Time to Leave" feature on iOS 10.3.2 causing multiple meeting invites in Exchange

Originator:ajtappa
Number:rdar://32898470 Date Originated:6/21/2017
Status:Closed Resolved:No
Product:iOS Product Version:10.3.2
Classification: Reproducible:Yes
 
Area:
Calendar

Summary:
Users running iOS 10.3.2 attaching to our Exchange environment are reporting seeing numerous meeting invites in their Outlook mailbox. These URLs detail the issue: https://blogs.technet.microsoft.com/ericwhitehill/2017/05/10/smart-forward-on-ios-devices-or-why-am-i-seeing-so-many-calendar-invites/  and https://support.microsoft.com/en-ie/help/4014990/meeting-invites-are-forwarded-by-an-attendee

After troubleshooting, the workaround for this problem is disabling the "Time to Leave" feature in iOS under Settings...Calendar...Default Alert Times...Time to Leave.

Steps to Reproduce:
Setup Exchange meeting, attach iOS 10.3.2 to account via Exchange ActiveSync and keep Time to Leave enabled. Set location of meeting to someplace other than where you are at, when it gets close to meeting time, dismiss the time to leave prompt. This causes the multiple meeting invites in the mailbox.

Expected Results:
User should not see any additional meeting invites being sent if Time to Leave is enabled on iOS.

Observed Results:
Multiple meeting invites show up in the user's Exchange mailbox.

Version:
iOS 10.3.2 (14F89)

Comments

Engineering has determined that your bug report (32898470) is a duplicate of 29145008 and will be closed.

The open or closed status of the original report your bug was duplicated to appears in a gray text box within the bug detail section of the bug reporter user interface. For security and privacy reasons, we don't provide access to the original bug yours was duped to.

By ajtappa at June 22, 2017, 2:21 p.m. (reply...)

Please note: Reports posted here will not necessarily be seen by Apple. All problems should be submitted at bugreport.apple.com before they are posted here. Please only post information for Radars that you have filed yourself, and please do not include Apple confidential information in your posts. Thank you!