Apple pay and Gpay not working since 7.9.2

  • Resolved Konrad

    (@konradkiss)


    2 months, 4 weeks ago

    Apple pay and Gpay not working since 7.9.2, gpay button is rendered even on non google capable platforms, apple pay ang gpay after trying to checkout blur the screen with no additional info or action, in console the following is displayed: 

    Uncaught (in promise) IntegrationError: When shippingAddressRequired is true, you must specify shippingRates.
        at z (v3/?ver=3.0:1:39439)
        at v3/?ver=3.0:1:347742
        at v3/?ver=3.0:1:340948
    WooCommerce: 		9.2.3	
    Action Scheduler: 	3.8.1
    WordPress:              6.6.1
    Server info: 		Apache
    PHP: 		        8.3.9	
    PHP post max size:      512 MB
    PHP time limit:         600
    PHP max input vars:     1000
    cURL : 		        7.81.0, OpenSSL/3.0.2
    SUHOSIN installed: 		–
    MySQL version: 		10.5.9-MariaDB-1:10.5.9+maria~focal-log	
    Max upload file size: 	256 MB
    • This topic was modified 2 months, 4 weeks ago by Konrad.

    The page I need help with: [log in to see the link]

Viewing 3 replies - 1 through 3 (of 3 total)

  • Hey there, @konradkiss! Thanks for contacting us. I’m happy to help you.

    While I was able to see the issue on your website, I was not able to replicate it on mine.

    The error you shared is regarding the address field being required.

    Are you using and plugins or custom code that affect the checkout page?

    Looking forward to your reply.

    Have a wonderful day!

    Thread Starter Konrad

    (@konradkiss)

    Dear @carolm29,

    Actually there is a shipping plugin and a custom code that affects only the tel. number field, adds the corresponding area code. In addition to this, after rolling back to 7.9.2 – everything works as expected.
    The need of filling out the shipping address breaks the logic of express checkout, therefore, the payment plugin from Woo is sadly not relevant for my installation anymore. :/ Is it possible to fix it in the new version, or only possible way is to use the 7.9.2 release?

    PS: please can you explain the google pay button showing up everywhere, even on non google platforms?

    Regards,

    The plugin – https://sk.www.ads-software.com/plugins/packeta/

    • This reply was modified 2 months, 3 weeks ago by Konrad.
    • This reply was modified 2 months, 3 weeks ago by Konrad.
    • This reply was modified 2 months, 3 weeks ago by Konrad.
    Plugin Support Shameem R. a11n

    (@shameemreza)

    Hi @konradkiss

    Actually there is a shipping plugin and a custom code that affects only the tel. number field, adds the corresponding area code. In addition to this, after rolling back to 7.9.2 – everything works as expected.

    The error you’re encountering appears to be related to the shipping address requirement. Since your setup includes a shipping plugin and custom code, it’s possible these could be interfering with the latest version of WooPayments.

    The fact that rolling back to version 7.9.2 resolves the issue suggests there may be a compatibility issue with your current setup and the newer version of the plugin.

    Please note that, Packeta is a third-party plugin, and we don’t provide help & support for custom code, 3rd-party plugins, or themes as they’re outside our support scope. It would be best to reach out to the plugin developer for further assistance.

    please can you explain the google pay button showing up everywhere, even on non google platforms?

    It’s designed to appear whenever the browser and device combination supports it. It’s not limited to Google platforms. If it’s appearing in unsupported environments, that could be an issue we need to investigate further.

    Meanwhile, if version 7.9.2 is functioning correctly for you, you may need to continue using it until that plugin or your custom code can ensure better compatibility with our plugin in future updates.

    I hope this provides some clarity. Please let us know if you have any other questions!

Viewing 3 replies - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.