microsoftgraph / microsoftgraph/msgraph-sdk-java
Issue with delta query causing JsonSyntaxException / EOFException in Java SDK 5.80.0
还没有人认领这个 Issue。
- 主要语言
- Java
- 星标
- 444
- 派生
- 154
- 平均合并
- 18 小时 28 分钟
- 30 天内合并 PR
- 4
描述
Describe the bug
SDK Version
com.microsoft.graph:microsoft-graph:5.80.0
API Endpoint
Error Trace
java.io.EOFException: End of input at line 1 column 6561 path $.value[7]
at com.google.gson.stream.JsonReader.nextNonWhitespace(JsonReader.java:1542)
at com.google.gson.stream.JsonReader.doPeek(JsonReader.java:550)
at com.google.gson.stream.JsonReader.hasNext(JsonReader.java:498)
at com.google.gson.internal.bind.TypeAdapters$28.read(TypeAdapters.java:875)
...
Wrapped by: com.google.gson.JsonSyntaxException: java.io.EOFException: End of input at line 1 column 6561 path $.value[7]
at com.google.gson.Gson.fromJson(Gson.java:1370)
at com.microsoft.graph.serializer.DefaultSerializer.deserializeObject(DefaultSerializer.java:104)
at com.microsoft.graph.http.CoreHttpProvider.handleJsonResponse(CoreHttpProvider.java:536)
Problem Description
When invoking the delta query on a mail folder using $skiptoken, the response causes a JsonSyntaxException due to malformed or truncated JSON — specifically during deserialization of the response.
It consistently fails at $.value[7], suggesting an incomplete or malformed JSON payload returned by the API or a decoding issue inside the SDK.
Expected behavior
The SDK should either:
Deserialize the full JSON response correctly;
Or raise a controlled exception indicating an incomplete/malformed response from the API.
How to reproduce
Call delta() on a MailFolder with large volume of messages.
Use the returned $skiptoken for the next page.
Observe the failure in Gson during deserialization of response.
Additional information
Status: 200, Headers: java.net.http.HttpHeaders@c17d2c61 { {:status=[200], cache-control=[private], client-request-id=[73d4281b-34fb-4316-8593-3141f23182ce], content-type=[application/json; odata.metadata=minimal; odata.streaming=false; IEEE754Compatible=false; charset=utf-8], date=[Fri, 25 Jul 2025 09:17:30 GMT], request-id=[73d4281b-34fb-4316-8593-3141f23182ce], strict-transport-security=[max-age=31536000], x-ms-ags-diagnostic=[{"ServerInfo":{"DataCenter":"East US","Slice":"E","Ring":"5","ScaleUnit":"004","RoleInstance":"BL02EPF00040ECF"}}]} }
SDK Version
5.80.0
Latest version known to work for scenario above?
No response
Known Workarounds
No response
Debug output
Click to expand log
```</details>
### Configuration
_No response_
### Other information
_No response_
贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
调研方向
从 DefaultSerializer.java 和 CoreHttpProvider.java 开始,报告的堆栈跟踪显示响应反序列化发生在这里;使用大型结果集和 $skiptoken 重现 mail-folder messages delta 请求。将 HTTP 响应正文与 $.value[7] 处的失败进行比较。当 SDK 能够在不发生未受控的 JsonSyntaxException 的情况下处理响应,或明确报告响应不完整时,即表示完成。
由索引模型根据 Issue 内容生成。
评估
- 技术栈
- java
- 领域
- api
- Issue 类型
- 缺陷
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 活跃度
- 停滞
- 描述清晰度
- 需要澄清
- 新手友好度
- 35/100