VDE SDK In-App Provisioning General response VP_ERROR_407

[akazawakaichi]

Hello, I'm a mobile application engineer currently responsible for developing in-app provisioning features using the VDE SDK.

I have a question about the VDE SDK's "VP_ERROR_407 SDKLockout" error response. My understanding is that this error occurs after a certain number of errors have accumulated.

How is this number counted? For example, if an error occurs in some process, does reinitializing the SDK and then encountering the same error again in the same process add to the count?

Thank you for your assistance.

[SyedSa]

Hi @akazawakaichi, Thank you for reaching out. An agent will get back to you as soon as possible. Until then, if any community member knows a solution, feel free to reply in this thread.

[DianaVisaPM]

Hey @akazawakaichi,

The "VP_ERROR_407 SDKLockout" error response in the Visa Digital Enablement (VDE) SDK typically occurs after a certain threshold of consecutive errors has been reached. This error is meant to prevent further actions when there have been repeated failures, which might indicate an issue that needs to be resolved before proceeding.

Regarding how the errors are counted, it's important to note that the count persists across SDK sessions. This means that simply reinitializing the SDK will not reset the error count. If an error occurs, and you reinitialize the SDK and encounter the same error again, it will add to the cumulative error count.

Here is an example of how the error counting might work based on your description:

```java
// START 
public void processInAppProvisioning() {
try {
// Initialize the VDE SDK
VDESdk vdeSdk = VDESdk.getInstance();
vdeSdk.initialize(context);

// Perform some provisioning process
vdeSdk.provisionCard(cardDetails);

} catch (VDEException e) {
if (e.getErrorCode() == VDEErrorCodes.VP_ERROR_407_SDKLockout) {
// Handle the SDK lockout error
System.out.println("SDK is locked out due to repeated errors.");
} else {
// Handle other errors
System.out.println("An error occurred: " + e.getMessage());
}

// Here we could reinitialize the SDK and try again, but note that
// the error count will not reset just by reinitializing
vdeSdk.reset(); // This does not reset the error count
}
}
// END 
```

In summary, the error count that leads to the "VP_ERROR_407 SDKLockout" persists across sessions and reinitializations. Therefore, encountering the same error after reinitializing the SDK will add to the count, potentially leading to the lockout if the error threshold is reached.