Crash ThreeDSecureClient

General information

• SDK/Library version: 4.15.0

• Environment: Sandbox

• Android Version and Device: Android 13

• Compile and Target SDK version: 33

• Braintree dependencies:

com.braintreepayments.api:card:4.15.0
com.braintreepayments.api:three-d-secure:4.15.0

Issue description

After calling method threeDSecureClient.performVerification it will crash. Stacktrace of the crash is below.

java.lang.SecurityException: Settings key: <data_roaming> is only readable to apps with targetSdkVersion lower than or equal to: 32
        at android.provider.Settings$NameValueCache.getStringForUser(Settings.java:3081)
        at android.provider.Settings$Global.getStringForUser(Settings.java:15854)
        at android.provider.Settings$Global.getString(Settings.java:15837)
        at com.cardinalcommerce.a.setLineHeight.<init>(:166)
        at com.cardinalcommerce.a.setHint.<init>(:23)
        at com.cardinalcommerce.a.setLineSpacing.Cardinal(:52)
        at com.cardinalcommerce.cardinalmobilesdk.Cardinal.configure(:5039)
        at com.braintreepayments.api.CardinalClient.configurationCardinal(CardinalClient.java:62)
        at com.braintreepayments.api.CardinalClient.initialize(CardinalClient.java:21)
        at com.braintreepayments.api.ThreeDSecureClient$1.onResult(ThreeDSecureClient.java:171)
        at com.braintreepayments.api.ConfigurationLoader.loadConfiguration(ConfigurationLoader.java:41)
        at com.braintreepayments.api.BraintreeClient$1.onAuthorizationResult(BraintreeClient.java:165)
        at com.braintreepayments.api.AuthorizationLoader.loadAuthorization(AuthorizationLoader.java:20)
        at com.braintreepayments.api.BraintreeClient.getAuthorization(BraintreeClient.java:174)
        at com.braintreepayments.api.BraintreeClient.getConfiguration(BraintreeClient.java:161)
        at com.braintreepayments.api.ThreeDSecureClient.performVerification(ThreeDSecureClient.java:133)

[sshropshire]

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.

[josephyanks]

@sshropshire - is there any update to this? We are having the same issue:

Settings key: <data_roaming> is only readable to apps with targetSdkVersion lower than or equal to: 32

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.