#michael_19345

1 messages · Page 1 of 1 (latest)

dense sailBOT
#

Hello! We'll be with you shortly. Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

slim agate
#

Can you share the code you're working with?

dense sailBOT
jagged harness
#

this happens when i click pay in google pay modal, then click the X after a few seconds. in the code this triggers the 'cancel' function. however, there is an error in the confirmPayment (i think)

junior cove
#

Gotcha, thank you. Looking in to this and will get back to you with what I can find

#

Do you know what line specifically gets that error?

jagged harness
#

i think it is the catch for the confirmPayment, not sure though as the dev log doesnt specify

junior cove
#

Can you try stepping through your code to confirm that?

jagged harness
#

its weird, this error triggers in the console a few secs after the cancel

#

it happens in Pay.js line 181

#

this is stripe code right

junior cove
#

Interesting, so you click on GPay, the sheet shows up, you close the sheet, and a few seconds later this error happens?

jagged harness
#

yeah

#

its seems to be some timing issue

#

related to confirmPayment

junior cove
#

I am not seeing this error myself on my own ECE page

jagged harness
#

so i was getting this error so then i added a try catch to confirmPayment. and now i get the other error im sharing with you

#

wait this one did fire too

#

a few secs after

#

this happens when you click pay and then cancel

#

can you reproduce this?

junior cove
#

Not happening for me unfortunately. Can you check your chrome version and send it to me, I can try in that specific version of chrome

#

Also can you successfully checkout with ECE in your page after this error shows up? Want to see if this affects behavior or is just polluting your console (which we would also want to address)