renovate: update major-risky-update #35

renovate · 2024-05-22T00:30:46Z

This PR contains the following updates:

Package	Type	Update	Change
gradle/actions	action	major	`v3` -> `v4`
com.stripe:stripeterminal-core	dependencies	major	`3.5.0` -> `4.1.0`
io.insert-koin:koin-androidx-compose (source)	dependencies	major	`3.5.6` -> `4.0.1`
co.touchlab.kmmbridge	plugin	major	`0.5.5` -> `1.2.0`
io.realm.kotlin	plugin	major	`1.16.0` -> `3.0.0`
io.realm.kotlin:library-base (source)	dependencies	major	`1.16.0` -> `3.0.0`
io.ktor:ktor-serialization-kotlinx-json	dependencies	major	`2.3.11` -> `3.0.3`
io.ktor:ktor-client-logging	dependencies	major	`2.3.11` -> `3.0.3`
io.ktor:ktor-client-auth	dependencies	major	`2.3.11` -> `3.0.3`
io.ktor:ktor-client-encoding	dependencies	major	`2.3.11` -> `3.0.3`
io.ktor:ktor-client-content-negotiation	dependencies	major	`2.3.11` -> `3.0.3`
io.ktor:ktor-client-darwin	dependencies	major	`2.3.11` -> `3.0.3`
io.ktor:ktor-client-cio	dependencies	major	`2.3.11` -> `3.0.3`
io.ktor:ktor-client-core	dependencies	major	`2.3.11` -> `3.0.3`
org.orbit-mvi:orbit-core	dependencies	major	`8.0.0` -> `9.0.0`
org.orbit-mvi:orbit-compose	dependencies	major	`8.0.0` -> `9.0.0`
io.insert-koin:koin-android (source)	dependencies	major	`3.5.6` -> `4.0.1`
io.insert-koin:koin-core (source)	dependencies	major	`3.5.6` -> `4.0.1`
com.google.devtools.ksp (source)	plugin	major	`1.9.24-1.0.20` -> `2.1.0-1.0.29`
org.jetbrains.kotlin.plugin.serialization (source)	plugin	major	`1.9.24` -> `2.1.0`
org.jetbrains.kotlin.multiplatform (source)	plugin	major	`1.9.24` -> `2.1.0`
org.jetbrains.kotlin.android (source)	plugin	major	`1.9.24` -> `2.1.0`

Warning

Some dependencies could not be looked up. Check the warning logs for more information.

Release Notes

gradle/actions (gradle/actions)

`v4`

Compare Source

stripe/stripe-terminal-android (com.stripe:stripeterminal-core)

`v4.1.0`

Core

Preview: Affirm support for smart readers is now available in private preview.
- If you are interested in joining this preview, please email [email protected].
New: Added a returnUrl parameter to ConfirmConfiguration to specify a desired URL to redirect to upon completion of a redirect payment method (such as Affirm).
Update: Added support for operating offline with simulated Bluetooth and USB readers.
Preview: Added a new enum value Manual to CardPresentCaptureMethod which will override the top level captureMethod set on the Paymentintent specifically for card_present transactions.
- If you are interested in joining this preview, please email [email protected].
Preview: Terminal::collectData will be supported on Smart readers.
- Note: This feature requires reader software version 2.28 or later to be installed on your smart reader.
- If you are interested in joining this preview, please email [email protected].
Fix: Fixed an issue where, if the SDK was initialized offline and a user immediately attempts to pair a reader offline, the first attempt fails with "The selected reader requires a software update", despite the reader being up-to-date.

Tap to Pay

New: Added error code TAP_TO_PAY_INSECURE_ENVIRONMENT for cases when payment collection is attempted in an insecure environment.

`v4.0.0`

4.0.0 includes breaking changes in both APIs and behavior. See the migration guide for more details.

Core

Add support for apps built with targetSdkVersion = 35 targeting Android 15 devices.

Note: This update includes support for Tap to Pay on Android. Users who were previously advised not to upgrade can now safely target version 35.

New Features

Mail order / telephone order (MOTO) payment support for smart readers.
- Contact Stripe support to enable this feature on your account.
Global card saving after payment support by updating customer consent capture. The following breaking changes are required:
- Removed the customerConsentCollected parameter from Terminal::collectSetupIntentPaymentMethod and replaced it with allowRedisplay.
- A valid allowRedisplay value is now required to be set in collectConfiguration when using setupFutureUsage for Terminal::collectPaymentMethod.

⚠️ Breaking changes required

Reader discovery

New: Added a new enum value DISCOVERING to ConnectionStatus to represent when discovery is running.
Update: InternetDiscoveryConfiguration now supports an optional timeout value, specifying the timeout in seconds for discover readers request. If the online discovery attempt fails, the operation automatically fall back to offline discovery.
Update: If a new discover operation is initiated while one is already in progress, the SDK will now cancel the ongoing operation with a CANCELED_DUE_TO_INTEGRATION_ERROR error and start the new operation.
Update: Internet and Tap to Pay discovery will now call the discoverReaders completion block when the operation completes since these are not long running discovery operations.
Update: Fields on the Location object are no longer mutable.

Reader connection

Update: There is now a single Terminal::connectReader method for all connection types. This replaces the previous methods: connectBluetoothReader, connectUsbReader, connectInternetReader, connectLocalMobileReader, and connectHandoffReader.
- For mobile readers, the readerListener parameter has been removed from the old connectBluetoothReader, connectUsbReader methods and moved into the respective ConnectionConfiguration object, replacing ReaderReconnectionListener.
- For Tap to Pay readers, the TapToPayConnectionConfiguration now takes in a TapToPayReaderListener parameter, replacing ReaderReconnectionListener.
- For smart readers, InternetConnectionConfiguration now takes in an InternetReaderListener parameter, which will alert your integration of events such as reader disconnects.
- For Apps on devices in handoff mode, HandoffReaderListener has been removed from the old connectHandoffReader method as a parameter, and moved into the HandoffConnectionConfiguration object.
Update: Auto reconnect on unexpected disconnect is now enabled by default for mobile readers and Tap to Pay readers.
- For mobile readers, ReaderListener has been renamed to MobileReaderListener and now extends ReaderReconnectionListener to provide a single interface for handling reader reconnection events.
- For Tap to Pay readers, TapToPayReaderListener extends ReaderReconnectionListener to provide a single interface for handling reader reconnection events.
- The ReaderReconnectionListener parameter has been removed from the connection configurations: LocalMobileConnectionConfiguration, BluetoothConnectionConfiguration, and UsbConnectionConfiguration.
- Auto-reconnect is now supported for simulated mobile readers. Users can now trigger events, such as ReaderReconnectionListener::onReaderReconnectStarted, by invoking Terminal::rebootReader.
- The ReaderReconnectionListener::onReaderReconnectStarted event has been updated to always include the DisconnectReason parameter, indicating the possible reasons for a mobile reader disconnection. For other reader types, UNKNOWN will be returned.
Update: The method for handling reader disconnects has changed.
- The TerminalListener::onUnexpectedReaderDisconnect has been removed. Implement onDisconnect on any of the following listeners to be informed of their corresponding reader disconnects: InternetReaderListener, MobileReaderListener, TapToPayReaderListener, or HandoffReaderListener.
- When auto-reconnect on unexpected disconnect is enabled, both onDisconnect and onReaderReconnectFailed methods will be called if the SDK fails to reconnect to the reader and it becomes disconnected.

Payment acceptance

Update: Terminal::confirmPaymentIntent, Terminal::confirmSetupIntent, and Terminal::confirmRefund now return a Cancelable, which allows you to cancel the operation in certain scenarios, such as QR Code payment presentment.
Update: Calls to Terminal::cancelPaymentIntent or Terminal::cancelSetupIntent will now cancel ongoing operations related to the specified intent.
Fix: Calls to Terminal::collectSetupIntentPaymentMethod now updates the provided SetupIntent with the correct status of SetupIntentStatus.REQUIRES_CONFIRMATION, instead of SetupIntentStatus.REQUIRES_PAYMENT_METHOD. Fixes issue 449.
Update: SetupIntent.id is now nullable to be consistent with Paymentintent.id. The SetupIntent.id will continue to be present.

Error handling

Update: Moved TerminalException.TerminalErrorCode to a standalone enum TerminalErrorCode.
Update: Introduced TerminalErrorCode.GENERIC_READER_ERROR. This error occurs when the SDK is out-of-date and can't map to a specific TerminalReaderError returned from a smart reader. The error message will be prefixed with "Error code: new_error_code."
- Empty error codes still result in TerminalErrorCode.UNEXPECTED_SDK_ERROR, but error message will be prefixed with "Error code: unknown."
- Known error codes continue to map to their corresponding TerminalErrorCode values, with unchanged error messages.

Renaming & refactoring

Update: Renamed ReaderListener to MobileReaderListener.
Renamed allowedPaymentMethodTypes to paymentMethodTypes:
- PaymentIntentParameters::allowedPaymentMethodTypes has been removed and replaced with PaymentIntentParameters::paymentMethodTypes.
- The allowedPaymentMethodTypes parameter in the PaymentIntentParameters.Builder constructors has been renamed to paymentMethodTypes.
- SetupIntentParameters::allowedPaymentMethodTypes has been removed and replaced with SetupIntentParameters::paymentMethodTypes.
- SetupIntentParameters.Builder::setAllowedPaymentMethodTypes has been removed and replaced with SetupIntentParameters.Builder::setPaymentMethodTypes.
Update: in ReaderSoftwareUpdate, rename UpdateTimeEstimate to UpdateDurationEstimate, and timeEstimate to durationEstimate.
Update: Converted java.util.Date references to timestamps in milliseconds for the following fields: ReaderSoftwareUpdate::requiredAt, OfflineDetails::storedAt and OfflineSetupIntentDetails::storedAt.

Tap to Pay

Update: The Maven coordinates for the Tap to Pay on Android feature have changed to com.stripe:stripeterminal-taptopay:4.0.0. Please update your build dependencies to point to the new artifact name. The old one will no longer be updated.
Update: SafetyNet Attestation API has been removed and replaced with Play Integrity API. Fixes issue 458.
Update: TapToPayConnectionConfiguration now takes in a TapToPayReaderListener parameter. This listener inherits events from both ReaderReconnectionListener and ReaderDisconnectionListener, providing a unified interface for handling reader events.
Update: The collectPaymentMethod and collectSetupIntentPaymentMethod now time out after 60 seconds for Tap to Pay on Android transactions. If a timeout occurs, a TerminalException will be raised with the error code CARD_READ_TIMED_OUT
Update: When PIN collection is requested for a payment, a TerminalException will be raised with error code FEATURE_NOT_ENABLED_ON_ACCOUNT instead of DECLINED_BY_STRIPE_API with an ONLINE_OR_OFFLINE_PIN_REQUIRED ApiError.
Update: "Local Mobile" has been renamed to "Tap To Pay" in all function names and error codes to align with Stripe branding:
- LocalMobileDiscoveryConfiguration has been renamed to TapToPayDiscoveryConfiguration.
- LocalMobileConnectionConfiguration has been renamed to TapToPayConnectionConfiguration.
- TapToPayConnectionConfiguration::localMobileReaderReconnectionListener has been renamed to TapToPayConnectionConfiguration::tapToPayReaderReconnectionListener.
- LocalMobileUxConfiguration has been renamed to TapToPayUxConfiguration.
- Terminal::setLocalMobileUxConfiguration has been renamed to Terminal::setTapToPayUxConfiguration.
- TerminalErrorCode::LOCAL_MOBILE_LIBRARY_NOT_INCLUDED has been renamed to TerminalErrorCode::TAP_TO_PAY_LIBRARY_NOT_INCLUDED.
- TerminalErrorCode::LOCAL_MOBILE_UNSUPPORTED_DEVICE has been renamed to TerminalErrorCode::TAP_TO_PAY_UNSUPPORTED_DEVICE.
- TerminalErrorCode::LOCAL_MOBILE_UNSUPPORTED_ANDROID_VERSION has been renamed to TerminalErrorCode::TAP_TO_PAY_UNSUPPORTED_ANDROID_VERSION.
- TerminalErrorCode::LOCAL_MOBILE_DEVICE_TAMPERED has been renamed to TerminalErrorCode::TAP_TO_PAY_DEVICE_TAMPERED.
- TerminalErrorCode::LOCAL_MOBILE_DEBUG_NOT_SUPPORTED has been renamed to TerminalErrorCode::TAP_TO_PAY_DEBUG_NOT_SUPPORTED.
- TerminalErrorCode::LOCAL_MOBILE_NFC_DISABLED has been renamed to TerminalErrorCode::TAP_TO_PAY_NFC_DISABLED.
- DeviceType::COTS_DEVICE has been renamed to DeviceType::TAP_TO_PAY_DEVICE.
The background application process used for collecting Tap to Pay transactions has been renamed to use your application's id, suffixed with :stripetaptopay.

`v3.10.1`

Tap to Pay

Fix: Prevent card reads after successful tap to prevent unintended secondary reads and improve transaction reliability.

`v3.10.0`

Core

Update: Add support for apps built with targetSdkVersion = 35 targeting Android 15 devices.
- Note: This update includes support for Tap to Pay on Android. Users who were previously advised not to upgrade can now safely target version 35.

`v3.9.5`

Apps on Devices: Handoff mode

Fix: Resolve additional edge case causing premature reader UI initialization.

`v3.9.4`

Apps on Devices: Handoff mode

Fix: Prevent reader UI from being started prematurely.

`v3.9.3`

Core

Fix: Prevent a crash that occurs when discovering bluetooth/usb readers and a timeout is set. Fixes issue 496.

`v3.9.2`

Core

Fix: Prevent a crash during reader connection on devices with marketing names containing non-ASCII characters. Fixes issue 495.

`v3.9.1`

Handoff

Fix: Handoff transactions do not complete

`v3.9.0`

Core

Beta: WeChat Pay support for smart readers is now available in private beta.
- If you are interested in joining this beta, please email [email protected].
Update: For mobile readers with auto reconnection enabled, the SDK now installs required updates upon reconnection after a reboot. Your application will continue to receive notifications about updates via the ReaderListener and should handle updating its UI to inform the user of the update accordingly.
Update: During bluetooth/usb reader discovery, the sdk now would only report updates through DiscoveryListener::onUpdateDiscoveredReaders when the list of discovered readers changes.
Update: Improved handling of READER_MISSING_ENCRYPTION_KEYS error for mobile readers with auto-reconnection enabled. Previously, the SDK would disconnect from the reader without auto-reconnecting when this error occurred. Now, if auto-reconnection is enabled, the SDK will automatically reconnect and recover from this error.
Fix: Fixed an issue where connecting to readers offline sometimes fails with "The selected reader requires a software update" despite the reader being up-to-date.

Tap to Pay (localmobile)

Update: Improved performance of reader connection
Update: Redesigned success screen for Tap to Pay transactions. The full-screen flood fill animation is replaced with a more subtle success indicator.

`v3.8.0`

Core

Update: compileSdkVersion is now set to 35 (Android 15 Beta).
- Note: SDK validation for targetSdkVersion 35 is in progress. Continue using targetSdkVersion 34 or lower until validation is complete in a future release.
Update: Deprecated PaymentIntentParameters::allowedPaymentMethodTypes & SetupIntentParameters::allowedPaymentMethodTypes replace with PaymentIntentParameters::paymentMethodTypes and SetupIntentParameters::paymentMethodTypes respectively.
Fix: Prevent a crash when attempting to connect to a mobile reader on Android devices that do not support Android Keystore cryptographic operations. Fixes issue 466.

Tap to Pay (localmobile)

New: Added customization options for the Tap to Pay prompt screen. Use Terminal.setLocalMobileUxConfiguration and LocalMobileUxConfiguration to set the configuration.
Update: Changed target version for classes from Java 7 to Java 8.

`v3.7.1`

Core

Fix: Prevent a crash when attempting to connect to a Bluetooth reader that has not already paired with this device yet. Fixes issue 473.

`v3.7.0`

Core

Beta: Surcharging is now available in private beta.
- Added a surchargeNotice parameter to CollectConfiguration to display a surcharge notice on the payment collection screen.
- Added a ConfirmConfiguration class to allow per-transaction overrides for confirmPaymentIntent.
- Added an amountSurcharge parameter to ConfirmConfiguration to surcharge when confirming a payment.
- If you are interested in joining this beta, please email [email protected].
Beta: Added a Terminal.collectData method to collect eligible magstripe data, such as gift cards, using a mobile reader.
- If you are interested in joining this beta, please email [email protected].
Update: Added SimulateReaderUpdateLowBatterySucceedConnect to simulate an error scenario where a required update fails on a mobile reader due to low battery, but the SDK still successfully connects to the reader.
- See Simulated reader updates for details.
Update: If a mobile reader receives the READER_MISSING_ENCRYPTION_KEYS error during payment collection, the SDK will disconnect from the reader. Note that auto reconnection will not work in this scenario. The error will automatically recover once the reader is reconnected.
Update: A callback to ReaderListenable::onReportReaderEvent will be triggered for card inserts/removals outside of a payment collection; this was previously only done during a payment. Resolves issue 446.
Fix: Removed delay in connecting to mobile reader due to queued discovery jobs when in offline mode.
Fix: Handle OutOfMemoryErrors from corrupted Log files to prevent application crashes. Fixes issue 464

Tap to Pay (localmobile)

Update: The background application process used for collecting Tap to Pay transactions has been renamed to use your application's id, suffixed with :stripelocalmobile.

`v3.6.0`

Core

Update: A callback to TerminalListener::onPaymentStatusChanged will be triggered when collecting inputs, with PaymentStatus.WAITING_FOR_INPUT.
Update: A callback to TerminalListener::onPaymentStatusChanged will be triggered when confirming a SetupIntent, with PaymentStatus.PROCESSING.
Update: TerminalException now includes an ApiError.setupIntent field, defined when the exception is an error returned from the Stripe API and related to a SetupIntent.
Update: Terminal.connectedReader's battery level will be updated whenever the mobile reader's battery info is reported. Fixes issue 423.
Update: If a reader receives the READER_MISSING_ENCRYPTION_KEYS error when collecting a payment the SDK now also reboots the reader in addition to the existing behavior of disconnecting from the reader. Reconnecting to the reader should re-install the keys and allow the reader to collect payments again.

Tap to Pay (localmobile)

Fix: The simulated reader now displays the transaction amount when collecting payments.
Fix: Prevent the reader from disconnecting when a payment is initiated with NFC disabled in the device settings. Fixes issue 380.

InsertKoinIO/koin (io.insert-koin:koin-androidx-compose)

Configuration

📅 Schedule: Branch creation - "after 10pm every weekday,before 4am every weekday,every weekend" in timezone Europe/Vienna, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

renovate bot added the dependencies label May 22, 2024

renovate bot force-pushed the renovate/major-risky-update branch from 5627b9a to c42c701 Compare May 23, 2024 09:58

renovate bot changed the title ~~renovate: update major-risky-update to v2~~ renovate: update major-risky-update May 23, 2024

renovate bot force-pushed the renovate/major-risky-update branch 2 times, most recently from 30778d8 to 46f3010 Compare June 5, 2024 23:16

renovate bot force-pushed the renovate/major-risky-update branch from 46f3010 to d8eb979 Compare June 11, 2024 17:15

renovate bot changed the title ~~renovate: update major-risky-update~~ renovate: update major-risky-update to v2 Jun 11, 2024

renovate bot force-pushed the renovate/major-risky-update branch 2 times, most recently from ab84ea0 to d674793 Compare June 17, 2024 13:23

renovate bot force-pushed the renovate/major-risky-update branch from d674793 to 245d32e Compare June 27, 2024 11:06

renovate bot force-pushed the renovate/major-risky-update branch from 245d32e to 123ff68 Compare July 5, 2024 19:02

renovate bot changed the title ~~renovate: update major-risky-update to v2~~ renovate: update major-risky-update Jul 5, 2024

renovate bot force-pushed the renovate/major-risky-update branch 2 times, most recently from d8e7be7 to 6ba9da4 Compare July 12, 2024 16:04

renovate bot force-pushed the renovate/major-risky-update branch 2 times, most recently from 4d7a812 to ce2119d Compare August 4, 2024 00:14

renovate bot force-pushed the renovate/major-risky-update branch 2 times, most recently from ea7a18e to 6777311 Compare August 6, 2024 23:48

renovate bot force-pushed the renovate/major-risky-update branch 3 times, most recently from b1f0c5d to c148487 Compare August 27, 2024 22:24

renovate bot force-pushed the renovate/major-risky-update branch 2 times, most recently from 6935fa9 to 0ecbde6 Compare September 5, 2024 22:58

renovate bot force-pushed the renovate/major-risky-update branch 3 times, most recently from 3cb1ad6 to 0ac54aa Compare September 17, 2024 11:57

renovate bot force-pushed the renovate/major-risky-update branch 3 times, most recently from 0341a42 to 6f4f517 Compare October 10, 2024 10:04

renovate bot force-pushed the renovate/major-risky-update branch from 6f4f517 to 1e8dbb7 Compare October 11, 2024 06:46

renovate bot force-pushed the renovate/major-risky-update branch 2 times, most recently from 1537ec9 to 5b71783 Compare October 29, 2024 22:44

renovate bot force-pushed the renovate/major-risky-update branch from 5b71783 to 84d6f01 Compare October 31, 2024 20:35

renovate bot force-pushed the renovate/major-risky-update branch from 84d6f01 to 4cb3b7c Compare November 7, 2024 22:57

renovate bot force-pushed the renovate/major-risky-update branch 2 times, most recently from bfc2e18 to 9f81ffd Compare November 19, 2024 01:53

renovate bot force-pushed the renovate/major-risky-update branch 3 times, most recently from 9561566 to 7b539e7 Compare December 3, 2024 19:56

renovate bot force-pushed the renovate/major-risky-update branch 2 times, most recently from 40a7baa to 3077fad Compare December 8, 2024 04:20

renovate bot force-pushed the renovate/major-risky-update branch 2 times, most recently from b2668d4 to f3b3abb Compare December 18, 2024 23:01

renovate: update major-risky-update

028347c

renovate bot force-pushed the renovate/major-risky-update branch from f3b3abb to 028347c Compare December 23, 2024 17:31

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

renovate: update major-risky-update #35

renovate: update major-risky-update #35

renovate bot commented May 22, 2024 •

edited

Loading

renovate: update major-risky-update #35

Are you sure you want to change the base?

renovate: update major-risky-update #35

Conversation

renovate bot commented May 22, 2024 • edited Loading

Release Notes

Core

Tap to Pay

Core

New Features

⚠️ Breaking changes required

Reader discovery

Reader connection

Payment acceptance

Error handling

Renaming & refactoring

Tap to Pay

Tap to Pay

Core

Apps on Devices: Handoff mode

Apps on Devices: Handoff mode

Core

Core

Handoff

Core

Tap to Pay (localmobile)

Core

Tap to Pay (localmobile)

Core

Core

Tap to Pay (localmobile)

Core

Tap to Pay (localmobile)

What's Changed

New Contributors

Configuration

renovate bot commented May 22, 2024 •

edited

Loading