microsoftgraph / msgraph-sdk-javascript

Microsoft Graph client library for JavaScript
https://graph.microsoft.com
MIT License
729 stars 220 forks source link

Activity and Availability Fields Missing in Payload for 'communications/presences' Subscription #1672

Closed yanoyuki closed 2 months ago

yanoyuki commented 2 months ago

Bug Report

Prerequisites

Description

When subscribing to presence updates via the Microsoft Graph SDK, the expected activity and availability fields in the resourceData object have gone missing in recent webhook payloads.

This issue has been affecting the functionality of our application as these fields are critical for monitoring user status.

https://learn.microsoft.com/en-us/graph/api/resources/presence?view=graph-rest-1.0#properties

Console Errors: [Is there any console error]

None

Screenshots: [If applicable, add screenshots to help explain your problem]

N/A

Steps to Reproduce

  1. Set up a new subscription for presence updates with the following code:
const subscription = await client.api('/subscriptions').post({
  changeType: 'updated',
  notificationUrl: "https://my-endpoint.example.com/presence",
  resource: `communications/presences/********`,
  expirationDateTime: "************",
});
  1. Receive a webhook notification payload.

  2. Observe that the activity and availability fields are missing from resourceData.

Expected behavior: [What you expected to happen]

The resourceData object should include activity and availability fields to provide full presence information.

Actual behavior: [What actually happened]

The resourceData object does not include activity and availability fields, affecting our application's functionality.

Additional Context

The absence of these fields began around 10:00 PM UTC on April 16, 2024, without any changes to our subscription setup or handling code. This issue appears to be systemic as it is consistently observed across multiple environments.

Usage Information

SDK Version - 3.0.7

Node Version - [18]

yanoyuki commented 2 months ago

I confirmed that the issue was fixed the following day.

Yesterday's Response Group 162

Today's Response Group 161