Skip to main content

18 posts tagged with "Android"

Android SDK releases

View All Tags

Android Push Provisioning v2.0.0

· 9 min read

Changes​

warning

This version is a major update over 1.0.0 that includes removals and changes in the public interface of the SDK, as well as a completely new distribution method. Make sure you address these changes by following the instructions in the migration guide at the end of the release notes for this version.

Compatibility​

Minimum Android SDK: 24 (Android 7.0 Nougat)

Compile SDK: 35

Target SDK: 35

Kotlin: 1.8.0 or newer

Weavr secure components SDK: v.3.3.0

Google Pay device requirements: Google Play services must be installed and up to date; NFC only needed for default-payment flows.

Added​

  • Added onCancelled() to AddToWalletListener.
  • Added WPPComponents.initializeWeavrSDK(context: Context, uiKey: String) to initialise the SDK instead of WPPComponents.initWeavrGPayClient.
  • Added WPPComponents.getCardStatus to replace WPPComponents.canAddCardToWallet avoiding listeners and using coroutines instead.
  • Added WPPComponents.setDefaultCardInGooglePay to replace WPPComponents.setCardAsDefaultPaymentMethod.
  • Added WPPException to subclass Exception for throwing, as well as to standardise the error reporting within the SDK. Note that the SDK won't be throwing and instead use Outcome to report success or error.
  • Added WeavrSDKErrorCodes to contain a list of error codes the SDK can use.
  • Added states PENDING and SUSPENDED to CardStatus.
  • Added multiple push provisioningPush Provisioning A method that allows cardholders to add their card to a digital wallet (such as Apple Pay or Google Pay) directly from your app. The card details are securely tokenized and sent to the wallet provider, streamlining the process and enhancing the user experience compared to manual provisioning. This feature is currently in beta. providers to maximise up-time and reliability.

Breaking changes​

  • Updated SDK access process—contact support@weavr.io to receive the latest package and onboarding instructions.
  • Changed WPPComponents.isGooglePayAvailable to be a synchronous method rather than using coroutines needlessly.
  • Changed onError(WPPException) in AddToWalletListener. This replaces the old onError(WPPError) as the WPPError type had less information on what went wrong.

Removed​

  • Removed WPPComponents.launchGpay as the result of WPPComponents.getPushProvisioningLauncher includes a provisionCard method instead.

Deprecated​

  • Deprecated WPPComponents.initWeavrGPayClient in favour of WPPComponents.initializeWeavrSDK.
  • Deprecated CardStatusListener in favour of an async method to get the card status.
  • Deprecated WPPComponents.canAddCardToWallet in favour of WPPComponents.getCardStatus.
  • Deprecated WPPComponents.setGPayAsDefaultNFCPaymentMethod in favour of WPPComponents.setGooglePayAsDefaultNFCPaymentMethod. This avoids using coroutines needlessly as the outcome depends only on whether the activity to select was able to be launched or not, not the actual result.
  • Deprecated WPPComponents.getGpayLauncher in favour of WPPComponents.getPushProvisioningLauncher to improve naming consistency.
  • Deprecated WPPComponents.setCardAsDefaultPaymentMethod with WPPComponents.setDefaultCardInGooglePay as the callback was unnecessary due to callback being called from within the method itself.
  • Deprecated WPPResult to be replaced with Outcome. This is because WPPResult would use an optional Success generic type, forcing users to account for nulls everywhere. Additionally made Outcome compatible with Kotlin Result by calling Outcome.asResult.
  • Deprecated the case Unknown of CardStatus, and added UNKNOWN for consistency across state capitalisation.
  • Deprecated the case GPayError of CardStatus. This state will no longer be used.

Other changes to note​

  • We have moved the SDK to work with AppCompactActivity preferably. Ensure that your activity is sub-classing it to avoid problems during provisioning.
  • SDK binaries are now distributed directly by Weavr Support—request access via support@weavr.io.

Android Components v3.0.1

· One min read

The Biometric Authentication component now supports the authentication of the end user via password rather than passcode. The password is used in two scenarios related to biometrics:

  1. As a pre-requisite to biometrics enrolment, to authenticate the user for the first time
  2. As a fall-back method of authenticating the user if biometrics fails (e.g. fingerprint not recognised)

Android Components v1.7.1

· One min read

These SDK releases were to backport the user-data collection fix from V2.0.1 to V1. This is so that embeddersEmbedder A company or developer that integrates Weavr's embedded finance services into their own application to provide financial services to their end customers. who do not use the Biometrics Authentication component, are not forced to adapt to the Safetynet removal breaking change.