#Srujan-paymentrequestbutton

1 messages · Page 1 of 1 (latest)

drifting panther
#

Hello! What do you mean by going to an earlier commit? If it's working in previous commits then even though very little has changed, the issue has to be related to the changes

arctic oyster
#

Yeah...I'm sure it's react related. Is there any odd behaviors that happen when canMakePayment is called multiple times?

#

I can get it to show sometimes and then it doesn't work after that

drifting panther
#

I feel like a better approach would be to compare the difference between the working and not working version and go from there

arctic oyster
#

I have but the changes are so minute so I went back to what I originally had and it worked for a second and goes after after a refresh

drifting panther
#

So the earlier commit is only sometimes working?

arctic oyster
#

No I believe it shows up every time

#

There was one error I had that I was curious about but it hasn't occurred but something about options.paymentRequest is immutable or something along those lines on my current local code. Could that be the root of the issue?

drifting panther
#

It's possible - what's the error you're seeing?

arctic oyster
#

I can't access it right now, it happened when I had the google pay button showing earlier but I cant get it to show. However, on the earlier commit I do notice that the google pay button shows once and after refresh it doesn't. I have to close the tab and reopen to get it to display again. Is this a browser related thing?

agile lance
#

Hi, karbi is stepping away - please give me a few moments to catch up

arctic oyster
agile lance
#

Can you specify the exact changes you've made?

arctic oyster
#

In terms on the PaymentButton component I completely went back to the original code that was working. All the changes were made on different pages and on my current code I commented out everything on the page so that there are no interactions and I'm just rendering the payment button

agile lance
#

I'm unable to open the link provided

arctic oyster
#

Do you get an error?

agile lance
#

No, trying another browser.

arctic oyster
#

Using chrome?

agile lance
#

Ok, it's working now - looking

arctic oyster
#

If you're done looking I'm going to go back to the current version I'm on and setup an ngrok link, I have something I want to try

#

I have a hunch that maybe my elements provider is too far up the tree

agile lance
#

Sure!

arctic oyster
#

Sweet thanks

agile lance
#

On that link you shared, I was able to see the Google Pay button so I'm unsure what the issue is now.

arctic oyster
#

That's my earlier commit

#

I have updated code where I can't get it to work, or I'l be able to get it to work once and then never again

#

I'll share a link soon

agile lance
#

I see, so can you compare the code between the two closely?

arctic oyster
#

Yeah

#

But I went back to the original code to a tee and it still doesn't show up

#

On this new link add a cart to the item and and follow steps to checkout page

agile lance
#

I can see the Google Button renders on this page as well

arctic oyster
#

Oh really?!

#

So it must be a local browser then

#

Why would my browser be behaving bad?

agile lance
#

Have you tried on different browsers?

arctic oyster
#

What other browser can I use to get google pay to show up?

agile lance
#

I meant, Incognito - sorry

arctic oyster
#

incognito doesn't work for me

#

still shows up blank

agile lance
#

I think it's your browser blocking something. Given that your other link was showing the button for you, you already have your Google wallet set up.

arctic oyster
#

Yup I think so

#

Could it be security issue with ngrok then?

#

I didn't think so before because I have it working from earlier. It's been pretty confusing to figure out why canMakePayment returns null on my new code

agile lance
#

What exactly did you change from link 1 to link 2?

arctic oyster
#

I did clear the cookies and now it seems to be showing up. I also allowed insecure content in settings

agile lance
#

Yeay!

arctic oyster
#

Hmm I think my chrome browser was blocking the button from showing best guess is insecure content