#Valentin Hinov
1 messages · Page 1 of 1 (latest)
Thanks! Give me a few minutes to look into this.
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?
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
Hello 👋
Taking over as soma needs to step away soon
Hey
The same happened yesterday to intent pi_3N8QHyKRNFCo7hZk07FWiMYU but that also seems to have went through OK
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?
yeah at that point I set the payment element to be read-only and don't update it
If you comment out that code, does the error go away?
I haven't managed to reproduce this - I've only seen reports from my live environment
I see. I wonder if its attempting to update the object while Apple Pay sheet is showing.
would an "update" be like updating the payment intent?
It could be. Basically once you click confirm, nothing should asynchronously update/change. Apple Pay is pretty sensitive about it