SDK Upgrade from CA Mobile-OTP-LIB-Android-2.2.5 to ca-mobile-authenticator-android-sdk-2.0.1 generate error for enrolled users
Article ID: 260463
CA Strong AuthenticationCA Advanced Authentication
Facing issues after upgrading the SDK of mobile app due to users enrolled with the old lib are no longer visible from the new one.
Release : Advanced Authentication 9.1
The new lib it is using a different database table to store data on the device and it seems that the user information already existing are no longer accessible.
For migration to work successfully from old application (integrated with AAFoundation SDK) to new application (integrated with AAFoundation SDK) -
Updated old application as follows
Integrate new AAFoundation SDK with old application
Implement CustomContentProvider.java as provided in attachment
Change all the application package names URI as per your new application package names, so that new application will get access to the storage of old application from where OTP account will migrate to the new application
Add READ PERMISSION for the CustomContentProvider, to access it from NEW application
Once migration is successful display a message to use new app for further authentication.
Publish old application to the Google Play
New application should be integrated with new SDK
Add fetchAndStoreAccounts() which handles the migration of accounts from Old application to new application
New application should be signed and published with the certificate which was used for the publishing of old application
For both the applications versions needs to be validated and initiate the migration action, so that the migration code exists on both the apps.