#jimmyt
1 messages ยท Page 1 of 1 (latest)
Hi
When you go to that docs page in Safari do you see the Apple Pay button at the top?
Are you using Connect?
I can see Apple Pay just fine
So likely is an issue with the card in your wallet that you are testing with
is there anyway to debug this. It would be really useful to get some sort of messagw somewher?
But great to know it's working - thank you very much ๐
Well visiting https://stripe.com/docs/stripe-js/elements/payment-request-button?client=html is usually the easiest way to tell in terms of testing out your own device/wallet.
If the Apple Pay button doesn't show at the top there then you know your wallet isn't set up correctly
With PaymentElement we basically just abstract this all away and only show the PaymentMethods that are supported
But i'm seeing the applepay button on that stripe test page but NOT in my app
So that implies my wallet is set up correctly?
Overall yes it should.
Can you screenshot what you see at the top of the docs page?
Huh that's strange
Same thing on my iphone
Where are you located?
UK
Ok that should be fine....
What did you select for your basket on your site?
Let me see if I can repro exactly what you did
weird
How do you get safari console - I always develop on chrome!
Right click + inspect Element
Cleared cache, nothing obvious in console
Interesting. Trying to think of what else this may be. I can see the Apple Pay button on your site as well.
I wish Apple Pay wasn't so opaque with its errors
any particular network calls I can look at
Unfortunately not aware of which ones may tell us more here. I will consult my colleagues and see if they have further debugging ideas
The response I get for this is: "An error occurred trying to load this response"
That is a call for Stripe telemetry. We'll fix it so that error doesn't pollute your dev console but it should not affect apple pay
๐
To double check, have you been in private mode when looking at any of these pages?
no - I was earlier but not now
Gotcha, can you try going to our test page in non-private mode and try to click on the button when it appears?
Sorry think I may have confused you. I've never been in private mode on my laptop.
I was in private mode on my iphone but not for a few hours now.
My apologies, can you still try clicking on the button just to make sure the expected cards show up?
yup
Thanks for checking. Still brainstorming debugging options
Do you have any other cards, maybe with different card brands, to add? I am not aware of brand restrictions but that does seem to be one of the only differences I can see between your setup and mine at the moment
i'll give it a try
same thing I'm afraid ๐ฆ
This seems like something more subtle is going on that we'll need to look into closely
Would you be able to write in to our support team with some example payments failing so we can investigate?
there are no failing payments - just ApplePay button failing to appear
just checked another iphone and it works on that.
but not on mine
I'm confused about your screenshot above then, which would appear after pressing the apple pay button
That's the issue.! It works on the stripe page but not in my website running on the same machine!
On safari on my laptop I see:
That implies my wallet is working.
I'm not able to load your page linked earlier right now
what country are you in?
Canada
Yep., works, and i see apple pay
So i'm really not sure what might be wrong for you here
Is there a knows set of checks that take place before displaying the applepay options. If so, is there any way of finding out which condition is not met.? Otherwise it is going to be hard for us to support our customers - asking "why can't I use applepay"?
Really these should be the only conditions that are required for your customers = https://stripe.com/docs/stripe-js/elements/payment-request-button?client=react#mobile-safari
there is really no trace or debug mode that can be switched on?
No, there isn't anything like that (which is why it's always tough for us to debug it ๐ข )
๐ฆ
are there any javascript calls o the browser I could write t to help narrow the issue down?
Let me think of what else I would suggest...
Just to make sure I have the current state - it's working for you on mobile, but not on your laptop right?