List Sessions call using expand segments failing with java.lang.UnsupportedOperationException: text does not support structured data

[priya2395]

Expected behavior

List Sessions call using expand segments should return list of sessions including segments

Actual behavior

List Sessions call using expand segments failing with java.lang.UnsupportedOperationException: text does not support structured data

Steps to reproduce the behavior

   final SessionCollectionResponse sessions = graphClient
            .communications()
            .callRecords()
            .byCallRecordId("e523d2ed-2966-4b6b-925b-754a88034cc5")
            .sessions()
            .get(requestConfiguration -> {
                requestConfiguration.queryParameters.expand = new String []{"segments"};
            });

[Ndiritu]

@priya2395 I'm unable to reproduce this behaviour. Would you mind sharing a stacktrace?

[sudhamadhuri]

Hi, is this issue fixed, can I get advice on this as I seem to have similar issue

[stherkildsen]

I have seen the same issue when updating a calendar event in a users calendar.
Stack-trace:
java.lang.UnsupportedOperationException: text does not support structured data at deployment.mscalendarsync.war//com.microsoft.kiota.serialization.TextParseNode.getObjectValue(TextParseNode.java:125) at deployment.mscalendarsync.war//com.microsoft.kiota.http.OkHttpRequestAdapter.lambda$throwIfFailedResponse$0(OkHttpRequestAdapter.java:674) at deployment.mscalendarsync.war//com.microsoft.kiota.ApiExceptionBuilder.<init>(ApiExceptionBuilder.java:26) at deployment.mscalendarsync.war//com.microsoft.kiota.http.OkHttpRequestAdapter.throwIfFailedResponse(OkHttpRequestAdapter.java:673) at deployment.mscalendarsync.war//com.microsoft.kiota.http.OkHttpRequestAdapter.send(OkHttpRequestAdapter.java:281) at deployment.mscalendarsync.war//com.microsoft.graph.users.item.calendar.events.item.EventItemRequestBuilder.patch(EventItemRequestBuilder.java:203) at deployment.mscalendarsync.war//com.microsoft.graph.users.item.calendar.events.item.EventItemRequestBuilder.patch(EventItemRequestBuilder.java:187)

[Ndiritu]

Thanks for reporting this @stherkildsen.

This seems like an issue during deserialization of some error payloads.

Would you mind sharing the response status code, headers & the body (please redact sensitive information) ?

[stherkildsen]

Is there a way to enable debug logging, that could expose the data you need. It only happens in our production environment, so I have only logging to go by.

…

On 3. sep. 2024 at 14.08, Philip Gichuhi ***@***.***> wrote: Thanks for reporting this @stherkildsen. This seems like an issue during deserialization of some error payloads. Would you mind sharing the response status code, headers & OData type of the body (please redact sensitive information) and sharing this with us? — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: ***@***.***>

[Ndiritu]

Hi @stherkildsen
You can enable OpenTelemetry using the snippet or use OkHttp's logging interceptor:

HttpLoggingInterceptor loggingInterceptor = new HttpLoggingInterceptor(System.out::println);
loggingInterceptor.level(HttpLoggingInterceptor.Level.BODY);
OkHttpClient.Builder builder = GraphClientFactory.create();
builder.addInterceptor(loggingInterceptor);
OkHttpClient okHttpClient = builder.build();
GraphServiceClient client = new GraphServiceClient(authProvider, okHttpClient);

[microsoft-github-policy-service]

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.