CA-mobile-authenticator-android-sdk-2.0.2 SDK – Known Issues and Fixes

Products

• CA Strong Authentication

Issue/Introduction

This KB article consolidates the known issues while integrating the Mobile Authenticator SDK, along with their root causes, impact, and resolutions. It also includes recommended component versions to ensure stability and compatibility.

• Application Crash During db.close()

  • The application crashes when invoking db.close(), and the following error is observed in logs: 
    
    A SQLiteConnection object for database '/data/user/0/it.nexi.test.nexisdkapp/databases/AccountsV2' was leaked!
    Please fix your application to end transactions in progress properly and to close the database when it is no longer needed.

• Resource Leak Warnings (Explicit termination method 'close' not called)

  • The following warnings appear in the application logs: 

    W/A resource was acquired at attached stack trace but never released. See java.io.Closeable
    java.lang.Throwable: Explicit termination method 'close' not called

• Recommended SQLCipher Version

  • For optimal compatibility and security, what SQLCipher version is recommended?

Cause

The Application Crash issue was caused by improper handling of database connections in earlier SDK versions, leading to leaked SQLite connections and a crash during database closure.

Resource Leak warnings occur due to a language mismatch between the customer application and the SDK:

• Your application: Kotlin

• SDK implementation: Native Java

Kotlin’s resource handling and lifecycle management differ slightly from Java, which leads to these warnings even though the resources are managed correctly at runtime.

Resolution

Application Crash During db.close()

The Application Crash issue has been successfully fixed in:

• AAFoundation_2_0_2

Upgrading to this version resolves the db.close() crash by ensuring database connections are handled and closed correctly.

Resource Leak Warnings (Explicit termination method 'close' not called)

These warnings are expected behavior in this scenario and do not indicate a functional issue. However, the SDK has been enhanced to explicitly address and suppress these warnings in:

• AAFoundation_2_0_3.jar

Upgrading to this version eliminates the warnings from the logs.

Recommended SQLCipher Version

For optimal compatibility and security, the following SQLCipher version is recommended: net.zetetic:sqlcipher-android:4.10.0. Using this version ensures proper encryption support and alignment with the SDK’s database handling logic.

Summary of Fixes

Issue	Impact	Fixed / Addressed In
db.close() crash	Application crash	AAFoundation_2_0_2
Resource leak warnings	Log warnings only	AAFoundation_2_0_3
SQLCipher compatibility	Stability & security	sqlcipher-android 4.10.0

Additional Information

 

Customers are strongly advised to upgrade to the latest available AAFoundation version in CA-mobile-authenticator-android-sdk-2.0.2 SDK to benefit from all fixes and improvements. If issues persist after upgrading, enable detailed logging and contact support with logs for further analysis.