#ceh_api

1 messages ยท Page 1 of 1 (latest)

tall sparrowBOT
#

๐Ÿ‘‹ Welcome to your new thread!

โฒ๏ธ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

โฑ๏ธ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

๐Ÿ”— This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1331390607452667914

๐Ÿ“ Have more to share? Add more details, code, screenshots, videos, etc. below.

proven wasp
#

Hi there

#

Could you share a link to a guide you're following to make these changes?

proven wasp
#

Are you following the iOS section of this guide? Do you have an example PaymentIntent that failed?

terse path
#

By IOS section do you mean Apple Pay? If yes, then yes, I am following these steps. I used apple pay before but with paymentIntentClientSecret to initalize payment sheet

#

and it was working fine

proven wasp
#

Okay, so which exact step is where you're blocked?

terse path
#
  1. It's customFlow
  2. in terms of configuration the only thing I changed is that I removed paymentIntentClientSecret and added :

intentConfiguration: {
mode: {
amount,
currencyCode
},
confirmHandler
},

  1. calling confirmPaymentSheetPayment on the checkout button press triggers apple pay that continuously processing and fails in the end
proven wasp
terse path
#
  1. is intentCreationCallback required?
  2. I am using react native
#

I see that confirmHandler is executed and payment method data is provided but apple pay sheet invoked by confirmPaymentSheetPayment fails for some reason

proven wasp
#

Give me a few minutes, I'll need to loop in a teammate who's more familiar with iOS development

tall sparrowBOT
tough seal
#

Hello! I'm taking over and catching up...

#

Hm, I thought we didn't support Apple Pay when using a custom flow. Let me check on that...

#

What version of the React Native Stripe SDK are you using?

terse path
#

"@stripe/stripe-react-native": "0.41.0"

tough seal
#

Do you have error logs from your app when this happens?

terse path
#

Steps 1-4 I already have completed because I used payment sheet with paymentIntentClientSecret before for apple payments

#

Step 5 I do also

tough seal
#

Okay, cool. What about the error logs?

terse path
#

Give me a few mins please. I will check

tough seal
#

In the meantime I found your support case and it looks like there's an outstanding internal issue for the product team to look at, so if nothing else you should recveive a response to that at some point. I don't have an ETA for you regarding that, though.

tough seal
#

You still around?

terse path
#

yes

#

spent some time building the app, providing output in a few secs

#

{"error": {"code": "Canceled", "declineCode": null, "localizedMessage": "The payment flow has been canceled", "message": "The payment flow has been canceled", "stripeErrorCode": null, "type": null}}

#

It's processing up to 10 seconds and then fails

tough seal
#

There are no other details? I would expect more verbose output from Xcode's debugger.

terse path
#

1 min pls

#

in the xcode console I only see these logs

tough seal
#

That's interesting... you're using a real, live card in Apple Pay, correct?

terse path
#

I am using simulator apple pay default provided card

tough seal
#

Ah, I'm not sure that's going to work. Can you try on a real device with a real card and see what happens?

terse path
#

Only in the morning, because it's too late for me now. It was working with paymentIntentClientSecret, though.

tough seal
#

It could be a bug in our SDK. Your best bet is probably to wait for a reply to your support case.

terse path
tough seal
#

I'm not certain if that flow works with Apple Pay or not. It should work, but I can't confirm. The reply to your support email should be able to confirm, though.