#Liuzhibin-iOS
1 messages · Page 1 of 1 (latest)
you can try to print out the paymentIntent.status and the error, to see what's their value
you would need to start debugging by knowing the data first
Wait a moment
hey
you see
status = STPPaymentHandlerActionStatusSucceeded , but paymentIntent.status = STPPaymentIntentStatusRequiresPaymentMethod
😢
card is 4000 000 000 3238
hey
Sorry, I am a bit swamped right now, will get back as soon as I can
okay
I'm pretty sure that's normal — the action (requesting the payment) succeeded, it's just that the outcome was a card decline.
but I'll test it.
But if it does, the SDK will fire Assert and cause a Crash
for iOS
you see
How can this be avoided,for iOS
I just tested that flow(I used 4000 000 000 3238 and got the authentication wrong).
I get back STPPaymentHandlerActionStatusFailed as expected.
can you give me a clear set of instructions to replicate the exact problem you see?
Please wait a moment
The test account I used was blacklisted on The Stripe management website,https://dashboard.stripe.com/
The test account was paid with a 3DSv2 verified credit card
There will be mistakes like this
The user has been blacklisted
hmm ok , I think I get it
so I should test using that 4000 000 000 3238 card, with a Customer object that has an email address on my Radar block list, and I should see the iOS SDK crash?
yes
interesting! I can try it out in a little bit and see if it happens to me
i use Stripe SDK 17.0.3
I know
why?
it's 2 years old
even if there is a bug here we're very unlikely to fix it, you should just use the latest version of the library.
It's a conundrum
not sure what you mean by that.