Closed jroyals closed 1 year ago
I have the same issue ! there is a problem inside pay.js
Same issue, reverting to logo-only for now but since 11pm last night we've not been able to take GPay payments because of the button not rendering with 'donate' or 'pay'. We haven't done a release, this appears to be an issue with externally-hosted pay.js.
Same here, the only options that work for me are buy
, plain
, short
and long
Same here.
Same here Is there a way to catch the error and hide the button?
Same for us, is there any way to load some exact version of pay.js?
Same here. If I revert button type to "buy" as mentioned above then it works although we prefer the "pay" option
The Google demo site is working again, I assume the underlying issue was fixed?
this was a temporary issue.
Describe the bug
Sorry I'm not sure if this is the right repo to report this but it's the closest I can find.
We use the Google Pay React button library in our project. Today we received reports our checkout was broken. Upon investigation we discovered that the "buttonType" property is causing an issue.
If a site specifies a buttonType that is anything other than "buy",
pay.js
will throw an exception and cause an error. In our situation the page became stuck and unresponsive. Once I removed this property and allowed the default, it worked again.I can reproduce this on the Google demo site.
To Reproduce
In this stack trace example I changed the buttonType to "donate" and it seems it is trying (and failing) to read a property of that string value.
Expected behavior
It works as we would expect
Component information:
At least the
pay.js
component.Environment:
Reproduced on Chrome for Windows, Chrome for Android and Chrome for iOS.