Android Push Provisioning v2.1.0
Maintenance release with dependency updates and improved Google Pay integration.
Push Provisioning SDK releases
View All TagsMaintenance release with dependency updates and improved Google Pay integration.
This version is a major update over v3.0.3 that includes breaking changes in the public interface of the SDK.
Make sure you address these changes by following the instructions in the migration guide at the end of the release notes for this version.
Introduction of a configuration file that is necessary to initialise dependencies. Change to initialisation method of the SDK. Removal of the card brand throughout the SDK since provider-routing is now handled automatically. Migration from event-based to Promise-based APIs.
This version is a major update over v1 that includes breaking changes in the public interface of the SDK.
Make sure you address these changes by following the instructions in the migration guide at the end of the release notes for this version.
WPPComponents.initialize(environment: , uiKey:).WPPComponents.makePassEntriesForCardsWith(authenticationToken:, entries:, imageFallback:).WPPComponents.addPaymentPass(authenticationToken: ,clientPaymentCardId: ,certificates: ,nonce: ,nonceSignature:) in case you prefer to avoid callbacks.reason, domain, underlyingErrorCode, and errorCode to WPPError to provide better context into what went wrong.WeavrProvisioningErrorCode and WeavrProvisioningErrorDomain to better represent errors. The end of this document contains appendixes with their values.AddCardToWalletStatus enum to better reflect the potential states a card can be in within Apple Pay.DeviceType enum to let you query the card status in a specific device between phone, or wallet. Also included an either value for convenience. The potential values and how to use them are listed in the Appendix.WeavrProvisioningExtensionHandler to simplify the non-ui wallet extension integration.WPPComponents.addPaymentPass(authenticationToken: ,clientPaymentCardId: ,certificates: ,nonce: ,nonceSignature: , completionHandler:) so that the PKAddPaymentPassRequest becomes nullable (PKAddPaymentPassRequest?). This allows to report failures to create the request, and is consistent with Apple's requirements in the PKIssuerProvisioningExtensionHandler.generateAddPaymentPassRequestForPassEntryWithIdentifier method.WPPComponents.makePassEntryForCardWith.WPPError.message in favour of newly added properties.WPPComponents.canAddCardToWallet(panLastFour:) in favour of WPPComponents.getCardStatusInWallet(forCardWithLastFourDigits:, deviceType:).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.
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.
onCancelled() to AddToWalletListener.WPPComponents.initializeWeavrSDK(context: Context, uiKey: String) to initialise the SDK instead of WPPComponents.initWeavrGPayClient.WPPComponents.getCardStatus to replace WPPComponents.canAddCardToWallet avoiding listeners and using coroutines instead.WPPComponents.setDefaultCardInGooglePay to replace WPPComponents.setCardAsDefaultPaymentMethod.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.WeavrSDKErrorCodes to contain a list of error codes the SDK can use.PENDING and SUSPENDED to CardStatus.WPPComponents.isGooglePayAvailable to be a synchronous method rather than using coroutines needlessly.onError(WPPException) in AddToWalletListener. This replaces the old onError(WPPError) as the WPPError type had less information on what went wrong.WPPComponents.launchGpay as the result of WPPComponents.getPushProvisioningLauncher includes a provisionCard method instead.WPPComponents.initWeavrGPayClient in favour of WPPComponents.initializeWeavrSDK.CardStatusListener in favour of an async method to get the card status.WPPComponents.canAddCardToWallet in favour of WPPComponents.getCardStatus.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.WPPComponents.getGpayLauncher in favour of WPPComponents.getPushProvisioningLauncher to improve naming consistency.WPPComponents.setCardAsDefaultPaymentMethod with WPPComponents.setDefaultCardInGooglePay as the callback was unnecessary due to callback being called from within the method itself.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.Unknown of CardStatus, and added UNKNOWN for consistency across state capitalisation.GPayError of CardStatus. This state will no longer be used.iOS Patch version to update one of our dependencies to include stability fixes.
iOS Patch version to update one of our dependencies to include stability fixes.
Fixes and stability improvements.
Fixes and stability improvements.
Stability and compatibility improvements to the Google Pay provisioning flow on Android, plus clearer results and error handling for embeddersEmbedder A company or developer that integrates Weavr's embedded finance services into their own application to provide financial services to their end customers..
Query from your app, whether a card is provisioned to a specific device (phone or watch).
Query from your app, whether a card is provisioned to a specific device (phone or watch).
Query from your app, whether a card is provisioned to a specific device (phone or watch).
Query from your app, whether a card is provisioned to a specific device (phone or watch).
This release performs two main changes:
The SDK exposes a new method WPPComponents.getCardStatusInWallet(forCardWithLastFourDigits:, deviceType:) that can be used to check the status of a given card within the Apple Pay wallet of the device.
Increases the scenarios under which AddToWalletButton will work.