3DS's ThreeDSecureResultCallback not triggered on Android13 device with targetSdkVersion to Android13.

[JammyZ]

General information

• SDK/Library version: 4.12.0 and 4.16.0
• Environment: Both Sandbox and Production
• Android Version and Device: Pixel 4 Android 13, Pixel 5 Android 13
• Braintree dependencies:
  "com.braintreepayments.api:card:4.12.0",
  "com.braintreepayments.api:samsung-pay:4.12.0",
  "com.braintreepayments.api:paypal:4.12.0",
  "com.braintreepayments.api:local-payment:4.12.0",
  "com.braintreepayments.api:union-pay:4.12.0",
  "com.braintreepayments.api:data-collector:4.12.0",
  "com.braintreepayments.api:three-d-secure:4.12.0",
  "com.braintreepayments.api:google-pay:4.12.0",
  "com.braintreepayments.api:american-express:4.12.0",
  'com.braintreepayments:card-form:5.4.0'

Issue description

My app is setting the targetSdkVersion to Android13.
The issue we faced is ThreeDSecureResultCallback is not response in release build after calling ThreeDSecureClient.performVerification on Android 13 devices. The 3DS verification code view is not displayed. I've tried the latest version 4.16.0, the issue persists. But it works fine on Android11/12 devices.
Do you have any idea?

[Pingapplepie]

We also wait for that BT developer team can adapt BT Android SDK to API Level 33.

[sshropshire]

Hi @Pingapplepie thanks for using the Braintree SDK for Android. We're waiting on Cardinal, our 3rd Party MPI for 3DS to provide an Android 13 update before we can provide official support for API Level 33.

They mentioned the update should come sometime soon in the next couple of weeks. We'll provide updates here as we get more information.

[JammyZ]

Hi @Pingapplepie thanks for using the Braintree SDK for Android. We're waiting on Cardinal, our 3rd Party MPI for 3DS to provide an Android 13 update before we can provide official support for API Level 33.

They mentioned the update should come sometime soon in the next couple of weeks. We'll provide updates here as we get more information.

Thank you @sshropshire . We will keep following this.

[jaxdesmarais]

Hey @JammyZ and @Pingapplepie -

This has been fixed by our 3rd Party MPI Cardinal. The fix has been released in version 4.18.0. Please let us know if you continue to run into this issue with their fix included after updating the SDK.