The Aera Wallets SDK releases are added to Sharepoint.

When using the SDK, we advise you to

• Ensure the SDK is updated as new versions are released by Aera
• Always pin SDK versions in your build system to avoid unexpected updates
• Monitor Aera’s changelog for breaking changes or migration steps

Updating SDK Versions

• Download the newest Wallets SDK version from Sharepoint
• Replace the old .aar Secure ID- and Wallets SDK files in your projects lib folder with the two new .aar files
• Gradle sync
• When relevant, update your code based on the updated Change logs

Verify Integrity of SDK releases

The Secure ID- and Wallets SDK are provided as signed .aar files, and the integrity can be verified by using the jarsigner tool.

Public Keystores found in Sharepoint include the certificates.

Example Wallets SDK

$ jarsigner -keystore android-wallets-sdk-keystore-debug-public.p12 -verify /<path>/aeraWalletsSDK-
debug.aar WalletsSDKDebug -storepass AeraWalletsSDKPublic1!

Example Secure ID SDK

$ jarsigner -keystore aarsign-public-debug.keystore -verify /<path>/AeraSdk-androidx-release-debug-
signed.aar aarsign -storepass AeraPublic1!