CheckMemberObject is retuning empty values

[ivanmaria]

I am trying to use checkMemberObject endpoint via msgraph-sdk-java v3.9.0. However, it is returning empty values instead of returning the list of ids. It works well via Postman.

I tried debugging and found that the response of checkMemberObject indeed contains list of ids but it is not being deserialized correctly.

Expected behavior

checkMemberObject output should produce list of ids.

Actual behavior

checkMemberObject output returns empty list.

Steps to reproduce the behavior

Refer the following snippet to reproduce the issue

graphServiceClient
.users("<id>")
.checkMemberObjects(DirectoryObjectCheckMemberObjectsParameterSet
    .newBuilder()
    .withIds(<list_of_ids>)
    .build())
.buildRequest()
.post();
.
.
.
// Verify the DirectoryObjectCheckMemberObjectsCollectionPage output

AB#9932

[baywet]

Hey @ivanmaria
Thanks for reaching out.
If you run the following code, what result do you get?

final String result = new DefaultSerializer(new DefaultLogger()).serializeObject(DirectoryObjectCheckMemberObjectsParameterSet
    .newBuilder()
    .withIds(<list_of_ids>)
    .build())

Also what version of the core library do you have?

[ivanmaria]

Hi @baywet

I am currently AFK so I wont be able to provide you the output immediately. However, this time the issue is while deserializing the response.

The core library version is 2.0.5 (via msgraph-sdk-java v3.9.0 dependency)

[baywet]

Thanks for the additional details. Core should be either 2.0.4 as required by the package or 2.0.6 as latest. Please update core as it contains a bug fixed with 2.0.6.

[ivanmaria]

Hi @baywet,

final String result = new DefaultSerializer(new DefaultLogger()).serializeObject(DirectoryObjectCheckMemberObjectsParameterSet
    .newBuilder()
    .withIds(<list_of_ids>)
    .build())

On running the above code, I get the following response:
{"ids":["2b530f8a-8520-48a1-a5ed-20eba6baabe8"]}

As I said earlier the issue is not with the Request but it is due to the deserialization of Response.

---

I checked the core library version and it was 2.0.4. However, according to these release notes the version should have been 2.0.5. Am I missing something here?

Anyway, I tried with the 2.0.6 version as well and the issue still persists. Could you look into it?

Thanks