-
Notifications
You must be signed in to change notification settings - Fork 236
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Crash ThreeDSecureClient #585
Comments
Hi, guys! Are there any estimates you can share with us on when this is potentially fixed? |
Hey @auxDK thanks for using the Braintree SDK for Android. We've reached out to Cardinal, our 3rd-party MPI on this issue. We'll report here when we have more information. |
Hi, we've encountered this issue on internal Android 13 builds. Same crash as mentioned above. We are using the latest drop-in UI dependency |
Hi @ersen-lw thank you for your feedback. We've been informed that this issue will be addressed in version |
We are having exact same issue and trying to support android 13. Please resolve this asap. Thank you.
|
@sshropshire - is there any update to this? We are having the same issue:
It's concerning how many issues we've bumped into regarding the Cardinal SDK and lack of support and proper testing for newer android versions. #594 seemingly is the same flavor of issue. |
I have definitely agree with @josephyanks. Braintree had Cardinal SDK issue with android 12 last year. Now it is same with android 13. Do we have to wait until next year for the resolution? |
It's worth pointing out that this issue is specific to SDK 32, which is android 12 (has been out for years). Just very frustrating, and costs us real $$. |
Same here, this is a big blocker to updating the SDK for us, using drop-in with version |
Hi all @josephyanks @bm185178 @joeboyscout04 the only update we've received is that a new release is coming soon. I agree this should have been caught much sooner. On the other hand, with API 32 still technically considered to be Android 12 this feels a lot like a hidden breaking change from Google, which can also happen from time to time. Also not making any excuses here, we'll work to integrate the fixed version as soon as it becomes available. We didn't provide explicit support for Android 12L with our SDK because we didn't see it as a huge ask from the community. I want to double down and say thanks to y'all for being both patient and vocal, this helps us to escalate the issue with Cardinal. I'm hoping we'll receive the update sometime soon in the coming weeks. |
@sshropshire |
Hello all - 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. |
General information
SDK/Library version: 4.15.0
Environment: Sandbox
Android Version and Device: Android 13
Compile and Target SDK version: 33
Braintree dependencies:
Issue description
After calling method
threeDSecureClient.performVerification
it will crash. Stacktrace of the crash is below.The text was updated successfully, but these errors were encountered: