This repository has been archived by the owner on Oct 18, 2023. It is now read-only.
forked from tipsi/tipsi-stripe
-
Notifications
You must be signed in to change notification settings - Fork 0
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
AppInfo is needed so that Stripe can identify the transactions that are created through tipsi-stripe Along with this, the compile and target SDK versions for android have been bumped to v28, stripe-android has been upgraded to 9.3.5, the minSdkVersion has increased to v19 (required). Example app changes: - Android compile and target SDK change from 26 -> 28 - Android min SDK change from 16 -> 19 - Android multiDexEnabled true - Android support libraries upgraded to v28 - React native upgraded to 0.59.10 - React upgraded to 16.8.6 - android.useDeprecatedNdk=true was removed since it is no longer supported. - android.enableAapt2=false was removed since it is now the default - Gradle build tools upgraded to 3.4.1. Gradle wrapper upgraded to v5.5.
- CircleCI config (for android) - Android - Compile SDK version increased from 26 to 28 - Android - Target SDK version increased from 26 to 28 - Android - Min SDK version increased from 16 to 19 - Android - stripe-android increased from 8.1.0 to 9.3.5 - Android - Added Stripe AppInfo to requests Example app: - Updated react-native to 0.59.10 from 0.45.0 - Updated react to 16.8.6 from 16.0.x - Upgraded gradle Tests: - Updated test suite to use webdriver 5.x from 4.7.1 - Update appium to 1.14
…he requiredBillingAddressFields-option
…and render the current docs
Note: This commit breaks iOS - a subsequent commit is needed Added confirmPayment, authenticatePayment, createPaymentMethod bindings for src/Stripe.js Upgrade to stripe-android:10.1.1
Note: This commit breaks iOS - a subsequent commit is needed
- Confirmation of a payment intent resolves with { status, paymentIntentId } - status is one of 'CANCELED', 'FAILED', 'SUCCEEDED', 'TIMEDOUT', or 'UNKNOWN' - test page requires 'STRIPE_BACKEND' env to be defined, and it should contain a URL with a trailing slash pointing to a deployment of https://github.com/mindlapse/example-tipsi-stripe-backend
Wiring in the new example app PaymentIntentScreen
…s the payment intent ends up in `succeeded` or `requires_capture` * If the resultingStatus of the PaymentIntent is either `succeeded`, or `requires_capture` then resolve the promise with `{ status: 'succeeded', ... }` * If the resultingStatus of the PaymentIntent is either `canceled`, `requires_action`, or `requires_confirmation`, then consider the payment intent to be `cancelled` and reject the promise. * Otherwise, consider the payment intent to be `failed` and reject the promise
…firmationSuccessStateOnAndroid Android: Allow requires_confirmation success state on android
…oid10.4 Android: Upgrade to latest stripe-android on the 10.4 line
Adds Stripe Connect Support. new JS method `setStripeAccount` which can be an account id or null.
[iOS] Fix extracting billingDetails
…or_on_ios_with_8.0.0.beta9 Bugfix/fix compilation error on ios for 8.0.0.beta9
Stripe Connect Support: Add setStripeAccount.
* Saving before trying android studio migrate * AndroidX conversion tweaks * AndroidX conversion tweaks Co-authored-by: Tomas Maly <tmaly1980@gmail.com>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.