Apple Pay on Single Product Page – Shipping Address Invalid error

We haven’t heard back from you in a while, so I’m going to mark this as resolved – if you have any further questions, you can start a new thread.

@wbrubaker — so, we should just report this one to WooCommerce support as a bug?

I have made a mistake. Sorry, I’ve reopened

@rogercoathup what is the URL where this problem is happening? What steps have you taken to troubleshoot?

@wbrubaker — it just failed (shipping address invalid) for me when I tried a subscription: https://www.golfersjournal.com/product/subscription/

Although, it worked currently when I tried a regular product (e.g. https://www.golfersjournal.com/product/tgj-broken-tee-shirt/). Previously it had failed on those as well.

It has worked consistently on checkout.

We tried on a stripped back site (when we first observed the problem ) — storefront, woo, woo subscriptions, stripe, but the problem remained.

When you go through the steps to cause this to happen, what is the browser console telling you? See: https://www.ads-software.com/support/topic/apple-pay-on-single-product-page-shipping-address-invalid-error/#post-12588684 for an example

thanks @wbrubaker — I’m a developer.

There’s a twitter related sniffer error, but nothing relevant to the Apple Pay issue.

A quick Google showed plenty of reports of this shipping address problem with Apple Pay.. not limited to Woo / Stripe

Here’s what I’m seeing. There is an AJAX call to ?wc-ajax=wc_stripe_add_to_cart

You can see in that screenshot that the HTTP response code is 403.

If we look at the response body we see that it is -1

That comes down to this line in code: https://core.trac.www.ads-software.com/browser/tags/5.4/src/wp-includes/pluggable.php#L1193

And what that means is that there is a nonce failure. This is generally caused by caching.

Just to chip in I did contact my hosting company re the Varnish 503 error and they came back with the following response:

Requests containing ?wc-ajax have been bypassed already,
The varnish 503 means that the PHP behind the request is failing, rather than an issue with Varnish itself. It’s likely a PHP or WordPress error.

The Varnish cache was disabled and the error still occurred but has since been re-enabled for my staging site. I was unable to investigate any further as I only have an iPhone\iPad which to my knowledge has limited browser developer tools (as far as I could see anyway).

Steve.

@wbrubaker — appreciate you taking a look.

I don’t receive the XHR error (either logged in / or out): screenshot

Would be good to know why you did, but I think that it’s a red herring with regard to the Apple Pay error.

• This reply was modified 4 years, 10 months ago by Roger Coathup.

Hi did you ever resolve this issue. We are seeing the same even with all plugins disabled??

Thanks ??

For my situation it worked to clear the cache that my plugin was doing

Hi did you ever resolve this issue. We are seeing the same even with all plugins disabled??

Thanks ??

No I did not. To be honest I tried rolling back versions of Stripe and WooCommerce, disabling Varnish my server based cache (and also disabling WordPress cache for css as well) and disabling all plug-ins leaving just WooCommerce and Stripe along with the StoreFront theme and the issue still occurred.

As mentioned earlier I not too fussed about this feature, although it is a nice to have it is not worth my time in troubleshooting and raising support tickets just trying to get it working.

One thing for sure is that it was working, and after updating either WooCoomerce or Stripe or both it stopped working. Other things may have updated behind the scenes but from my perspective it was a couple of plug-in updates and ‘boom’ things broke.

Hi @stepfaul

We have been looking into what I believe is the same error as a team. There is now an open public Issue around this – https://github.com/woocommerce/woocommerce-gateway-stripe/issues/1193

The scenario we’ve found is that for some UK addresses, only Apple Pay reports an invalid address. The address looks correct on the shop pages and there is no problem when using Google / Chrome Pay.

Can you confirm this is happening for every address you try or only certain ones, @stepfaul @rogercoathup

As mentioned earlier I not too fussed about this feature, although it is a nice to have it is not worth my time in troubleshooting and raising support tickets just trying to get it working.

We’d love to get to the bottom of this, so if you can replicate it, please do reach out to us, mentioning that GitHub link and this forum post. We can then tie reports together and with more examples of this error, we can have a better chance of finding the cause.

Thanks,

I’m going to mark this one as resolved for now. The development team will be looking into this with the linked Issue above as reference.

Thanks,