Office-js: Office.context.mailbox.item.recurrence.getAsync throws error

[gguiceaccru]

When making a call to Office.context.mailbox.item.recurrence.getAsync on an existing recurring appointment it throws the following error:

Uncaught TypeError: Cannot read property 'startYear' of undefined at SeriesTime.importFromSeriesTimeJsonObject (outlook-web-16.01.debug.js:13514) at seriesTimeJsonConverter (outlook-web-16.01.debug.js:14879) at outlook-web-16.01.debug.js:9783 at Object.invokeResponseCallback [as callback] (outlook-web-16.01.debug.js:9819) at _receive (outlook-web-16.01.debug.js:4650)

Expected Behavior

Returns the entire Recurrence object for the appointment series.

Current Behavior

The above error is thrown. If I debug SeriesTime.prototype.importFromSeriesTimeJsonObject it looks like the jsonObject parameter being passed is occasionally undefined causing the aforementioned error.

Steps to Reproduce, or Live Example

1. Access the outlook web application
2. Create a recurring appointment (in my case I've been trying a daily recurrence for 4 days).
3. Open the recurrence for editing (single occurrence "this" edit, "this and followng" edit, or entire series edit)
4. Attempt to make the Office.context.mailbox.item.recurrence.getAsync call.

Context

I need the recurrence information to properly display information to the users of our outlook add-in.

Your Environment

• Platform [PC desktop, Mac, iOS, Office on the web]: Office on the web
• Host [Excel, Word, PowerPoint, etc.]: Outlook
• Office version number: latest of office on the web on August 4th 2020
• Operating System: MacOS
• Browser (if using Office on the web): Chrome

Useful logs

• [x] Console errors
• [x] Screenshots
• [ ] Test file (if only happens on a particular file)
  Uncaught TypeError: Cannot read property 'startYear' of undefined at SeriesTime.importFromSeriesTimeJsonObject (VM14 outlook-web-16.01.debug.js:13514) at seriesTimeJsonConverter (VM14 outlook-web-16.01.debug.js:14879) at VM14 outlook-web-16.01.debug.js:9783 at Object.invokeResponseCallback [as callback] (VM14 outlook-web-16.01.debug.js:9819) at _receive (VM14 outlook-web-16.01.debug.js:4650)

[lindalu-MSFT]

Thanks for following our template when opening this issue! It will help our team triage faster. I assigned this to the Mac Outlook team. Cheers, lindalu

[exextoc]

We are able to reproduce this from our side. Thanks for reporting this issue. It has been put on our backlog. We unfortunately have no timelines to share at this point

[lstableford-mb]

I am also experiencing this error when just generally attempting to retrieve recurrence using .getAsync. Whether the appointment is new or existing is not a factor. The call fails to resolve or reject consistently on every single occasion, with the error shown above logged in the console.

[chathumdavton]

We are able to reproduce this from our side. Thanks for reporting this issue. It has been put on our backlog. We unfortunately have no timelines to share at this point

This is a significant issue as this is happening for all recurrence patterns. Please provide us with an ETA of a fix.

[SWei1234]

I also met this problem on both safari and chrome. Hope this will be fix soon.

[exextoc]

Apologies for the delay. We are working on fixing this. Fix will be out soon.

[SWei1234]

@exextoc Cool! : )

[SWei1234]

Hi @exextoc
Can we have an ETA about this?
Or which month will Microsoft release this?
Thanks

[t-soares]

I am also facing the same issue with an Outlook add-in.

[simon-kavanagh]

@exextoc any update on release timeline? We have in production customers impacted by this.

[exextoc]

The fix is ready and is being deployed, it should be available globally by 31/08

[ghivert]

Hi, it looks like it’s still not upgraded. When can we expect to see the fix in production?

[SWei1234]

Hi @exextoc
It looks still not fixed yet. Is the deploy delay?
Thanks

[exextoc]

Apologies, the deployment got delayed. Fix should now be available early next week.

[SWei1234]

@exextoc
Got it. Will check it after Microsoft's deploy.

[SWei1234]

Hi @exextoc
Hi, I'm glad to see this morning that this problem doesn't recur.
But a new problem arose.
After I schedule a new recurring meeting with zoom add-in, Then I choose 'Discard' and the meeting still saved.
Is hte logic changed? Before this deploy, the meeting will not be saved When I click 'Discard'.
Any idea?
Thanks

[exextoc]

@SWei1234 There is no logic change here. We are not able to repro this at our end. Can you please share repro video?

[Texaner]

Hi @exextoc, @SWei1234
Same here.
I have an Add-In in development and need to save the recurring appointment during the creation.
If I choose 'Discard', the appointment is still saved in the calendar.
This only affects recurring appointments, for normal single appointments it works as expected.

[exextoc]

@Texaner Can you please share OWA build number?

[MrAshRhodes]

Hi,
This is the error when clicking Discard on a recurring meeting.

"Cannot read property 'isMeeting' of null''

[Texaner]

@Texaner Can you please share OWA build number?

@exextoc
Where can I find the build number?
In the source code I found the following:

    <meta name="scriptVer" content="20200831001.08" />
    <meta name="physicalRing" content="WW" />
    <meta name="environment" content="Prod" />
    <meta name="preload" content="true" />
    <meta name="baseUrl" content="//outlook-1.cdn.office.net/owamail/20200831001.08/" />
    <meta name="backupUrl" content="//outlook-2.cdn.office.net/owamail/20200831001.08/" />

Is that enough for you?

[MrAshRhodes]

If this is any help, in the http response headers i found the following.

x-owa-owsversion: V2018_01_18
x-owa-version: 15.20.3348.16

[Texaner]

@exextoc
nx-owa-owsversion: V2018_01_18 x-owa-version: 15.20.3348.16

[SWei1234]

Hi @exextoc
Sure.

Recording:
https://success.zoom.us/rec/share/gtQEszcTdqsgSDr5bzNApoBxj0VGJZCeSCXi_qOtLygOMOb73CscDHQEw8pZ_XAM.R6XoXgkF4pfF0XCv

Access Passcode: diMHH#R0

[Texaner]

Here is the exact error. Maybe this is helpful

[exextoc]

@SWei1234 @Texaner @MrAshRhodes Thank you for sharing details on issue. This will be helpful. We are investigating this issue.

[MrAshRhodes]

Quick update, the error is still persistent. although if you click on the "Try Again" the meeting will get cancelled.
I'm guessing the fact that the meeting exists on the second time the 'isMeeting' value is _true_ and can remove the meeting from the calendar.

Hi,
This is the error when clicking Discard on a recurring meeting.

"Cannot read property 'isMeeting' of null''

[msftbot[bot]]

This issue has been automatically marked as stale because it is marked as needing author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment. Thank you for your interest in Office Add-ins!

[SWei1234]

Hi @exextoc
Is there any ETA about this?
Thanks

[msftbot[bot]]

This issue has been automatically marked as stale because it is marked as needing author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment. Thank you for your interest in Office Add-ins!

[SWei1234]

Hi @exextoc
Is the repair time of the problem derived from the repair of the problem available?
Thanks

[jbaptistehuguenin]

Hi @exextoc we are having the same problem here with our Outlook add-:in: no Recurrence object is returned for the appointment series.
Can you please update us on on your investigation ?
It sounded like a solution was about to be released and then no news, and then a bot message that the issue will be closed !

[exextoc]

Hey all,

Unfortunately, we are still investigating this issue. Please do use the Graph API as a workaround for getting the recurrence of the meeting till this is resolved: https://docs.microsoft.com/en-us/graph/outlook-schedule-recurring-events

[exextoc]

Hi, looks like there are multiple issues being talked about here, causing confusion.

1. recurrence.getAsync throws error / returns null - This issue has been fixed from our end on OWA. recurrence.getAsync() shouldn't be returning null anymore. We aren't able to reproduce this bug from our end any more. If you're in organizer mode, make sure you call recurrence.getAsync() and not item.recurrence.

Please verify this on your end and let us know if you're still able to reproduce it.

1. Discarding a meeting still saves it - This is not related to the original issue, so please create a new issue for it.

[SWei1234]

Hi @exextoc @jbaptistehuguenin @Texaner @MrAshRhodes
I created an new ticket for this issue:
https://github.com/OfficeDev/office-js/issues/1405
Thanks

[msftbot[bot]]

This issue has been automatically marked as stale because it is marked as needing author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment. Thank you for your interest in Office Add-ins!

[msftbot[bot]]

This issue has been closed due to inactivity. Please comment if you still need assistance and we'll re-open the issue.