Skip to content

renovate: update major-risky-update #35

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented May 22, 2024

This PR contains the following updates:

Package Type Update Change Age Adoption Passing Confidence
gradle/actions action major v3 -> v4 age adoption passing confidence
com.stripe:stripeterminal-core dependencies major 3.10.2 -> 4.5.0 age adoption passing confidence
io.insert-koin:koin-androidx-compose (source) dependencies major 3.5.6 -> 4.1.0 age adoption passing confidence
co.touchlab.kmmbridge plugin major 0.5.5 -> 1.2.1 age adoption passing confidence
org.orbit-mvi:orbit-core dependencies major 8.0.0 -> 10.0.0 age adoption passing confidence
org.orbit-mvi:orbit-compose dependencies major 8.0.0 -> 10.0.0 age adoption passing confidence
io.insert-koin:koin-android (source) dependencies major 3.5.6 -> 4.1.0 age adoption passing confidence
io.insert-koin:koin-core (source) dependencies major 3.5.6 -> 4.1.0 age adoption passing confidence

Release Notes

gradle/actions (gradle/actions)

v4

Compare Source

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

v4.5.0

Core
New
Updates
  • The Terminal.collectInputs method to display forms and collect information from customers is now generally available, and it no longer requires an opt-in annotation.
  • Preview: The ConfirmConfiguration.amountSurcharge field has been renamed to ConfirmConfiguration.surcharge.amount.
    • If you are interested in joining this preview, please contact Stripe support.
Tap to Pay
Updates
  • Improved messaging for Play Integrity API failures during the reader connection process. Fixes issue 580.

v4.4.0

Core
New
Fixes
  • Terminal operations that require a connected reader (e.g. collectPaymentMethod) will now fail with TerminalErrorCode.NOT_CONNECTED_TO_READER when no reader is connected.
Tap to Pay
New
Fixes
  • Gracefully handle device-to-device restore for apps that use the android:allowBackup="true" manifest tag. Fixes issue 513.
  • Terminal.supportsReadersOfType() will now return false when checking Tap to Pay on Android compatibility for host devices that do not support certain hardware-backed KeyStore operations. Fixes issue 553.
  • Prevent Tap to Pay reader connections from failing on devices without an accelerometer. Fixes issue 562.

v4.3.1

Core
  • Fix: Prevent crashes in applications using newer versions of Sentry. Fixes issue 566.

v4.3.0

Core
Tap to Pay
  • New: On-screen PIN entry is now generally available on Tap to Pay Android.
  • Breaking: When Tap to Pay Android PIN throws a TerminalException due to an insecure condition the exception will have a correct errorCode of TAP_TO_PAY_INSECURE_ENVIRONMENT instead of TAP_TO_PAY_DEVICE_TAMPERED.
  • Fix: Prevent a StringIndexOutOfBoundsException crash on certain device models prior to showing the Tap to Pay payment screen. Fixes issue 533.
  • Update: Improved error messaging when Tap to Pay on Android PIN fails due to an insecure condition.

v4.2.0

Core
  • New: Added error code READER_TAMPERED for detecting if a mobile reader is tampered on connection.
  • Fix: Addressed an issue where readers lose optional software updates after auto-reconnecting.
Tap to Pay
  • New: HIDE_OVERLAY_WINDOW permission is now required for Tap to Pay to ensure a secure environment while operating.
  • Fix: Allow the Tap to Pay reader to connect from applications that have enabled installer checks in Google Play. Fixes issue 866.
  • Fix: Localization issues for Tap to Pay on Android PIN preview.

v4.1.0

Core
  • Preview: Affirm support for smart readers is now available in private preview.
  • 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.
  • Preview: Terminal::collectData will be supported on Smart readers.
  • 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

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 Callback.onSuccess method as part of discoverReaders 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
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: Reduce the amount of time Terminal::connectReader takes to complete attestation.

  • Update: Improve acceptance of some cards that previously would have displayed "Please use another card"

  • 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.

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

v4.1.0

Compare Source

What's Changed
New Contributors

Full Changelog: InsertKoinIO/koin@4.0.4...4.1.0

v4.0.4

Compare Source

What's Changed

Full Changelog: InsertKoinIO/koin@4.0.3...4.0.4

v4.0.3

Compare Source

What's Changed
New Contributors

Full Changelog: InsertKoinIO/koin@4.0.2...4.0.3

v4.0.2

Compare Source

What's Changed
New Contributors

Full Changelog: InsertKoinIO/koin@4.0.1...4.0.2

v4.0.1

Compare Source

What's Changed
New Contributors

Full Changelog: InsertKoinIO/koin@4.0.0...4.0.1

v4.0.0

Compare Source

What's Changed

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 renovate bot force-pushed the renovate/major-risky-update branch from 5627b9a to c42c701 Compare May 23, 2024 09:58
@renovate renovate bot changed the title renovate: update major-risky-update to v2 renovate: update major-risky-update May 23, 2024
@renovate 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 renovate bot force-pushed the renovate/major-risky-update branch from 46f3010 to d8eb979 Compare June 11, 2024 17:15
@renovate renovate bot changed the title renovate: update major-risky-update renovate: update major-risky-update to v2 Jun 11, 2024
@renovate 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 renovate bot force-pushed the renovate/major-risky-update branch from d674793 to 245d32e Compare June 27, 2024 11:06
@renovate renovate bot force-pushed the renovate/major-risky-update branch from 245d32e to 123ff68 Compare July 5, 2024 19:02
@renovate renovate bot changed the title renovate: update major-risky-update to v2 renovate: update major-risky-update Jul 5, 2024
@renovate 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 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 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 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 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 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 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 renovate bot force-pushed the renovate/major-risky-update branch from 6f4f517 to 1e8dbb7 Compare October 11, 2024 06:46
@renovate renovate bot force-pushed the renovate/major-risky-update branch 2 times, most recently from e0a9880 to 962b730 Compare February 27, 2025 22:50
@renovate renovate bot force-pushed the renovate/major-risky-update branch from 962b730 to f846087 Compare March 6, 2025 19:40
@renovate renovate bot force-pushed the renovate/major-risky-update branch 3 times, most recently from 1927c16 to 9d1a42c Compare March 21, 2025 06:37
@renovate renovate bot force-pushed the renovate/major-risky-update branch 4 times, most recently from 3253a89 to c6f4740 Compare March 27, 2025 12:59
@renovate renovate bot force-pushed the renovate/major-risky-update branch from c6f4740 to 3d3b4f1 Compare March 31, 2025 19:12
@renovate renovate bot force-pushed the renovate/major-risky-update branch 3 times, most recently from 6c389e7 to afee4eb Compare April 9, 2025 23:31
@renovate renovate bot force-pushed the renovate/major-risky-update branch from afee4eb to 562ee5a Compare April 23, 2025 22:24
@renovate renovate bot force-pushed the renovate/major-risky-update branch 5 times, most recently from 1552f1c to 7d98d84 Compare May 7, 2025 23:09
@renovate renovate bot force-pushed the renovate/major-risky-update branch 3 times, most recently from 38e0fec to af7bbb9 Compare May 14, 2025 06:37
@renovate renovate bot force-pushed the renovate/major-risky-update branch 3 times, most recently from c49ddc4 to fc992ac Compare May 28, 2025 10:11
@renovate renovate bot force-pushed the renovate/major-risky-update branch 2 times, most recently from fcd46c6 to a7626f5 Compare June 9, 2025 10:39
@renovate renovate bot force-pushed the renovate/major-risky-update branch from a7626f5 to 63a26a0 Compare June 10, 2025 19:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants