[BUG] Face liveness results not accessible after completing verification

[mahdi-almousawi]

Library name and version

Azure.AI.Vision.Face 1.0.0-beta.2

Describe the bug

I'm using the Azure.AI.Vision.Face library to create Liveness with Verification Sessions, and everything works fine initially. But when I try to fetch the results for a completed liveness session, I'm getting the following exception:

The requested operation requires an element of type 'String', but the target element has type 'Number'.

This issue occurs only after performing the liveness and verification operation on the mobile SDK. For newly created sessions where results are not yet available, I can retrieve the results without any problems.

It seems that when results are available, additional data or formatting is coming from Azure that is not being handled correctly by the SDK.

Expected behavior

When fetching the results for a completed liveness session using the Azure.AI.Vision.Face library, the library should return the session's results in the expected format without throwing any exceptions.

Actual behavior

When I try to fetch the results for a completed liveness session, I'm getting the following error message from the SDK:

The requested operation requires an element of type 'String', but the target element has type 'Number'.

Please note that this issue occurs only after performing the liveness and verification operation on the mobile SDK. For newly created sessions where results are not yet available, I can retrieve the results without any problems.

Reproduction Steps

The following code creates a new Liveness with Verification session, this works without any issues:

var body = new CreateLivenessWithVerifySessionContent(LivenessOperationMode.Passive) {
      SendResultsToClient = false,
      DeviceCorrelationId = deviceId,
      AuthTokenTimeToLiveInSeconds = authTokenTimeToLiveInSeconds
};

var response = await faceSessionClient.CreateLivenessWithVerifySessionAsync(body, verifyImage);

The following code retrieves the results for the given sessionId, this only works for newly created sessions:

var response = await faceSessionClient.GetLivenessWithVerifySessionResultAsync(sessionId);

Environment

• Azure.AI.Vision.Face 1.0.0-beta.2
• JetBrains Rider 2024.2.1

Dotnet Info (running from Docker container)

Host:
  Version:      8.0.10
  Architecture: x64
  Commit:       81cabf2857
  RID:          linux-x64

.NET SDKs installed:
  No SDKs were found.

.NET runtimes installed:
  Microsoft.AspNetCore.App 8.0.10 [/usr/share/dotnet/shared/Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 8.0.10 [/usr/share/dotnet/shared/Microsoft.NETCore.App]

Other architectures found:
  None

Environment variables:
  Not set

global.json file:
  Not found

[github-actions]

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @dipidoo @Han-msft @leareai @longli0 @lulululululu @ShaoAnLin.

[mahdi-almousawi]

Hi everyone, any updates?

[yst-msft]

Hi @mahdi-almousawi , thank you for reporting the issue. We'll fix it in the next release. In the meantime, you might want to use the method below as a workaround. You can access the raw output from response.ContentStream.

Response response = await faceSessionClient.GetLivenessWithVerifySessionResultAsync(sessionId, null);

[SangNguyenTL]

JObject.Parse(result.Content.ToString())

When I parse the raw response structure myself, I get a response like this, which is also not good when returning results to the client.

[SangNguyenTL]

The API is returning a number instead of a string for the imageType field. When do we have a plan for this issue? Can I submit a contribution to this issue?

azure-sdk-for-net/sdk/face/Azure.AI.Vision.Face/src/Generated/LivenessOutputsTarget.Serialization.cs

Line 107 in 539c9b0

imageType = new FaceImageType(property.Value.GetString());

[doolse]

Any update on this? There is a new API version (v1.3-preview.1) any plans to release a new .NET SDK?