CA Mobile Authenticator SDK Compatibility with Android API Target Level 36

Products

• CA Strong Authentication

Issue/Introduction

Customers integrating the CA Mobile Authenticator SDK into Android applications may need to comply with new Google Play Store requirements mandating the use of Android API Target Level 36.

Whether CA Mobile Authenticator SDK version 2.2.3 is fully compatible with compileSdkVersion 36 and targetSdkVersion 36 and whether any known limitations or required SDK changes exist for this migration?

Environment

 

CA Mobile Authenticator SDK (CA Advanced Authentication):

• Android Authenticator SDK
• Android AuthID SDK
• Android DDNA SDK

 

Resolution

The current CA Mobile Authenticator SDK was originally built using:

• compileSdkVersion 34
• targetSdkVersion 35

However, customers can independently update their Android application configuration to:

• compileSdkVersion 36
• targetSdkVersion 36

without requiring modifications to the existing SDK integration.

Our engineering team has confirmed that the SDK functions correctly when the host application targets Android API Level 36.

As part of an internal validation initiative for Android API Target Level 36 compliance:

• The CA Mobile Authenticator SDK target SDK has been updated to version 36
• The SDK has been rebuilt successfully
• Validation testing completed successfully within Broadcom internal application environments

Although Google Play Store enforcement for previously published applications targeting lower SDK versions has not yet fully restricted updates or publishing, Broadcom recommends adopting the newly validated SDK versions as a preventive and safeguard measure moving forward.

Broadcom recommends using the newly validated Android SDK components for all future mobile authenticator integrations targeting API Level 36.