#Valentin Hinov

1 messages · Page 1 of 1 (latest)

hard heartBOT
stone crater
#

Hi there!

#

Can you share a PaymentIntent ID (pi_xxx) where you saw this issue?

alpine juniper
#

Sure, it's pi_3N8il9KRNFCo7hZk0e7sH00x I believe

#

They used Apple pay apparently

stone crater
#

Thanks! Give me a few minutes to look into this.

stone crater
#

Sorry for the delay.

#

I don't see any errors on the PaymentIntent.

#

Can you clarify exactly when you saw the error you mentioned above in your flow?

alpine juniper
#

My error logs report it happening just as the user initiates the payment

#

but it seems to go through fine afterwards

#

i don't think the user was affected

hard heartBOT
lofty ingot
#

Hello 👋
Taking over as soma needs to step away soon

alpine juniper
#

Hey

#

The same happened yesterday to intent pi_3N8QHyKRNFCo7hZk07FWiMYU but that also seems to have went through OK

lofty ingot
#

The error seems to be coming from your client-side code. Something in your code is trying to update options object after you call confirmPayment

Have you looked into what happens after you call confirm function?

alpine juniper
#

yeah at that point I set the payment element to be read-only and don't update it

lofty ingot
#

If you comment out that code, does the error go away?

alpine juniper
#

I haven't managed to reproduce this - I've only seen reports from my live environment

lofty ingot
#

I see. I wonder if its attempting to update the object while Apple Pay sheet is showing.

alpine juniper
#

would an "update" be like updating the payment intent?

lofty ingot
#

It could be. Basically once you click confirm, nothing should asynchronously update/change. Apple Pay is pretty sensitive about it

alpine juniper
#

Hmm ok - I'll have a look in the code again

#

thanks for the help