Receiving FaceLiveness.FaceLivenessDetectionError Code 1

[haarj]

Describe the bug

Some of my users are receiving
FaceLiveness.FaceLivenessDetectionError Code 1, which in the iOS SDK is a session not found error in FaceLivenessDetectionError.swift file,
public static let sessionNotFound = FaceLivenessDetectionError( code: 1, message: "Session not found.", recoverySuggestion: "Enter a valid session ID." )

We are creating a sessionID server side, passing the session ID to the FaceLivenessDetectorView constructor and receive the above error.

Steps To Reproduce

Follow steps above

Expected behavior

Faceliveness Detector view sequence starts and accepts valid sessionID.

Swift Liveness Version

1.2.14

Xcode version

15.4

Relevant log output

No response

Is this a regression?

No

Regression additional context

No response

OS Version

17.5.1

Device

iPhone 11 Pro

Specific to simulators

No

Additional context

This is intermittent. This happens to some users and we are not sure why.

[sebaland]

Hi @haarj, thanks for opening this issue!

Would you mind telling us how you are triggering the creation of the session id on the server side? Also, do you have any relevant logs that you can share?

Thanks!

[haarj]

Hey @ruisebas sure thing. I can't reproduce it on my side. It happens to my users sometimes and it's hard to know why or acquire logs.

Here is how I am calling it server side.

const rekClient = new Rekognition({
      region: "us-east-1",
      credentials: {
            accessKeyId: rekAccessKeyID,    
            secretAccessKey: process.env.AMAZON_REKOGNITION_SECRET_KEY
        }
    });
const response = await rekClient.createFaceLivenessSession().promise();
const sessionId = response.SessionId;
console.log("SessionId:", sessionId);

[sebaland]

Thanks for providing the code. I assume you are triggering this server code in your app, for example with a Amplify.API.post call, right?

Are you certain that you are receiving a valid response from the service before attempting to show FaceLivenessDetectorView?
Or putting it in another way, are you handling error responses so that FaceLivenessDetectorView is not being invoked with an old or default sessionId?

[haarj]

Hey @ruisebas my server side code is always returning a "valid" session Id, which is then passed back to the app and then passed to the FaceLivenessDetectorView immediately. What makes this a valid or invalid session ID I'm not sure. Is there a race condition happening where the sessionID I am creating server-side is not recognized by the detector view yet, maybe?

[sebaland]

Hi @haarj, following up on this.

While a race condition would cause this, I think it's unlikely to happen since the session creation is performed on the backend itself. Are you sure you're passing the correct region to the Liveness component?

To get more information, would you be able to log these failing session ids and provide them, alongside their time of creation and region? We can then involve the service team and ask them to verify if the sessions are indeed created or what could be going on.

Thanks!

[sebaland]

Oh and sorry to insist on this, but how are you handling errors when attempting to create the session?

const response = await rekClient.createFaceLivenessSession().promise();
const sessionId = response.SessionId;

I'm not really familiar with NodeJS, so what happens if createFaceLivenessSession returns an error?
Are you propagating it to your app and handling it inside a do catch block?

[haarj]

Hey @ruisebas I'll have to release a new version to capture this information. Standby on that front. I'll admit that I don't receive errors on the backend side of things when creating session Ids and so the apps always receive "valid" sessions Ids.

[sebaland]

Thanks!

I think that might be the cause, createFaceLivenessSession () failing and the function returning an invalid/corrupted sessionId that is then attempted to be used.

[haarj]

Yea so it seems that every now and then a bad sessionID gets created. Anything I can do on my end to fix that?

[sebaland]

To be precise, it's not like a bad sessionId is created, but rather that the CreateFaceLivenessSession call fails. So a session is never created.

This is outside the scope of the Liveness component, but what you should do is inspect the reason for the failure. You might want to propagate the error to the application so you can handle it gracefully (e.g. showing an error alert/screen instead of trying to show the Liveness component)