`channels().post()` returns `null` when creating a shared channel (`membershipType: shared`)
還沒有人認領這個 Issue。
評估
研究方向
先在 graphClient.teams().byTeamId(teamId).channels().post(channel) 重現共用頻道的情況，並將其 202 回應與標準頻道和私人頻道的 201 回應進行比較。閱讀 Microsoft Graph 的共用頻道建立文件，並檢查 SDK 的回應處理；完成條件是針對非同步回應採用已議定的行為，或是在不進行 API 變更的情況下提供明確且有文件記載的處理方式。
由索引模型根據 Issue 內容生成。
描述
Describe the bug
When creating a channel with membershipType set to ChannelMembershipType.Shared, the graphClient.teams().byTeamId(teamId).channels().post(channel) method returns null instead of a Channel object.
This works correctly for standard and private channel types, which return the expected Channel object.
Root cause analysis
According to the Microsoft Graph API documentation (Example 5 — Create a shared channel), creating a shared channel returns an HTTP 202 Accepted with a Location header pointing to a teamsAsyncOperation, whereas standard/private channels return a 201 Created with the Channel object in the response body.
The SDK's .post() method appears to only handle the 201 Created case, deserializing the response body into a Channel object. When it receives a 202 Accepted (with no Channel in the body), it returns null without providing access to the response headers or the async operation.
This is the same issue reported in the .NET SDK: microsoftgraph/msgraph-sdk-dotnet#1728
Expected behavior
One of the following:
-
Preferred: The SDK should detect the 202 Accepted response, follow the Location header, poll the teamsAsyncOperation until completion, and return the resulting Channel object — providing a consistent developer experience across all channel types.
-
Alternative: The SDK should return a wrapper type (e.g., ChannelPostResponse) that can represent either a Channel (for 201) or a TeamsAsyncOperation (for 202), along with the Location/Content-Location headers.
-
Minimum: The documentation should clearly state that .post() returns null for shared channels, and provide a documented pattern to retrieve the channel using NativeResponseHandler (or equivalent in Java).
How to reproduce
ChannelMembershipType type = ChannelMembershipType.Shared;
Channel channel = new Channel();
channel.setOdataType("#Microsoft.Graph.channel");
channel.setMembershipType(type);
channel.setDisplayName("My Shared Channel");
channel.setDescription("Test shared channel creation");
LinkedList<ConversationMember> members = new LinkedList<>();
AadUserConversationMember conversationMember = new AadUserConversationMember();
conversationMember.setRoles(List.of("owner"));
HashMap<String, Object> additionalData = new HashMap<>();
additionalData.put("[email protected]",
"https://graph.microsoft.com/v1.0/users('" + ownerId + "')");
conversationMember.setAdditionalData(additionalData);
members.add(conversationMember);
channel.setMembers(members);
// This returns null for shared channels, but works for standard/private
Channel result = graphClient.teams().byTeamId(teamId).channels().post(channel);
System.out.println(result); // null
SDK Version
6.62.0
Latest version known to work for scenario above?
6.62.0
Known Workarounds
None
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 天 新手友好度 35/100
microsoftgraph/msgraph-sdk-java#2589 · 1 則留言 ·
查看 microsoftgraph/msgraph-sdk-java 的全部 Issue
相似的 Issue
-
1.0.0-rc2
難度 2/5 1-3 小時 新手友好度 68/100
wso2/dpdp-accelerator#377 ·
維護者通常 1 天內回覆
-
area/dependencies backport/26.4 kind/cve severity/high source/scan-dependencies status/triage
難度 2/5 1-3 小時 新手友好度 85/100
維護者通常 2 天內回覆
-
(primitive-collections-base) Use `NumberInput` to parse numeric map keys, as `jackson-databind` does未關閉
難度 2/5 1-3 小時 新手友好度 78/100
FasterXML/jackson-datatypes-collections#270 ·
維護者通常 1 天內回覆
-
type/bug
難度 2/5 1-3 小時 新手友好度 88/100
維護者通常 1 天內回覆
-
bug
難度 2/5 1-3 小時 新手友好度 68/100
維護者通常 1 天內回覆