Error in PATCH onlineMeeting
還沒有人認領這個 Issue。
評估
研究方向
首先，使用 Java SDK 6.64.0 重現針對 onlineMeetings endpoint 的 PATCH 要求，使用 allowAttendeeToEnableCamera，並觀察是否傳送了 @odata.type。將該要求與文件中預期的 200 回應以及 getBackingStore().clear() workaround 進行比較；當 PATCH 成功且無需手動清除 backing store 時，即表示完成。
由索引模型根據 Issue 內容生成。
描述
Describe the bug
Hello,
I have integrated microsoft graph sdk to programmatically manage onlineMeetings. Since a couple of days I am getting errors in updating onlineMeetings (PATCH methods) even with this simple request:
PATCH https://graph.microsoft.com/v1.0/users/<owners_uid>/onlineMeetings/
{
"@odata.type": "#microsoft.graph.onlineMeeting",
"allowAttendeeToEnableCamera": true
}
response:
{
"error": {
"code": "InvalidArgument",
"message": "One or more properties do not support updating. Please refer to Microsoft Graph documentation for more information.",
"innerError": {
"date": "2026-05-11T09:52:54",
"request-id": "c33e69dd-de32-4030-a393-d6cd63a449ea",
"client-request-id": "c33e69dd-de32-4030-a393-d6cd63a449ea"
}
}
}
as a workaround I have used object.getBackingStore().clear(); just after its creation before passing it to the patch. This will delete the parameter "@odata.type": "#microsoft.graph.onlineMeeting" making it work again.
EDIT 2026-05-11 08:07:00: at the moment issue seems to have been fixed.
Expected behavior
PATCH https://graph.microsoft.com/v1.0/users/<owners_uid>/onlineMeetings/
{
"@odata.type": "#microsoft.graph.onlineMeeting",
"allowAttendeeToEnableCamera": true
}
returns 200 with updated onlineMeeting
How to reproduce
try to patch an existing meeting using the java sdk for example setting the parameter allowAttendeeToEnableCamera
sdk under the hood will automatically add
"@odata.type": "#microsoft.graph.onlineMeeting"
to the http patch
it used to work in the past, but since a couple of days it returns:
"error": {
"code": "InvalidArgument",
"message": "One or more properties do not support updating. Please refer to Microsoft Graph documentation for more information.",
SDK Version
6.64.0
Latest version known to work for scenario above?
No response
Known Workarounds
as a workaround I have used object.getBackingStore().clear(); just after its creation before passing it to the patch. This will delete the parameter "@odata.type": "#microsoft.graph.onlineMeeting" making it work again.
Debug output
Click to expand log
```</details>
### Configuration
_No response_
### Other information
_No response_- 主要語言
- Java
- 星號
- 445
- 分支
- 154
- 平均合併
- 18 小時 28 分鐘
- 30 天內合併 PR
- 4
環境準備
- 沒有 Dockerfile 或 Docker Compose 檔案
- 有 Pull Request 範本
- 閱讀貢獻指南
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
microsoftgraph/msgraph-sdk-java 的其他 Issue
-
status:waiting-for-triage type:bug
難度 2/5 1-3 小時 新手友好度 68/100
microsoftgraph/msgraph-sdk-java#2610 ·
-
status:waiting-for-triage type:bug
難度 3/5 1-2 天 新手友好度 55/100
microsoftgraph/msgraph-sdk-java#2656 ·
-
status:waiting-for-triage type:bug
難度 4/5 3-5 天 新手友好度 38/100
microsoftgraph/msgraph-sdk-java#2654 ·
-
status:waiting-for-triage
難度 4/5 3-5 天 新手友好度 35/100
microsoftgraph/msgraph-sdk-java#2639 ·
-
status:waiting-for-triage type:bug
難度 3/5 1-2 天 新手友好度 68/100
microsoftgraph/msgraph-sdk-java#2587 ·
查看 microsoftgraph/msgraph-sdk-java 的全部 Issue
相似的 Issue
-
bug
難度 2/5 1-3 小時 新手友好度 78/100
liquid-java/liquidjava#321 ·
維護者通常 2 天內回覆
-
難度 1/5 1 小時以內 新手友好度 88/100
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 82/100
OpenConext/OpenConext-access#1015 ·
維護者通常 1 天內回覆
-
68000: FDBcc branch target is 2 bytes too low (uses inst_start+2 instead of the displacement word)未關閉
難度 2/5 1-3 小時 新手友好度 82/100
NationalSecurityAgency/ghidra#9702 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 85/100
apache/rocketmq-dashboard#5358 ·
維護者通常 3 天內回覆