Issue with delta query causing JsonSyntaxException / EOFException in Java SDK 5.80.0

DefaultSerializer.java と CoreHttpProvider.java から始めます。報告されたスタックトレースにはレスポンスのデシリアライズが示されているため、大規模な結果セットと $skiptoken を使用して mail-folder messages の delta リクエストを再現します。HTTP レスポンス本文と $.value[7] での失敗を比較します。SDK が制御されない JsonSyntaxException を発生させずにレスポンスを処理するか、不完全なレスポンスであることを明確に報告できれば完了です。

Describe the bug

SDK Version
com.microsoft.graph:microsoft-graph:5.80.0

API Endpoint

`GET https://graph.microsoft.com/v1.0/users/{user-id}/mailFolders('{folder-id}')/messages/delta?$skiptoken={...}

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

</details>


### Configuration

_No response_

### Other information

_No response_