#TheMechanic
1 messages · Page 1 of 1 (latest)
Hello TheMechanic, we'll be with you shortly! Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
• https://discord.com/channels/841573134531821608/1163488269024108585, 3 days ago, 33 messages
• https://discord.com/channels/841573134531821608/1163462661653135430, 3 days ago, 34 messages
Hey there, is this specifically using cross-origin framing for apple pay in safari 17?
Is there a live site we can access to see this behaviour?
I'm trying with iframe only
you can try it there : https://prestashop-qa.getjust.eu/fr/home/21-51-t-shirt-doge.html#/8-color-blanc/26-size-xs
(button buy in one click)
Hey there, still looking at this, ut having issues trying to load the framed page directly
we can't load the framed page directly, as we need informations sent by postmessage from the main frame
it seems we got issues with Gpay too
so i guess we are doing something wrong
as it used to work before
I keep looking at our code to see what changes have been done, that could be the root cause of this
Can you say more about the google pay issues?
It does seem like you have some internal cross domain issues too, based on console errors i see
top domain wasn't registered in test mode, i added it, but it does'nt change anything
the google pay issue is kind of the same, it tries to pay, but fails
I have to find out what we are doing wrong, and if it's front or back
thanks for your help
This is definitely needed, but you say it hasnt changed the result?
Google Pay doesn't have the same framing limitations as apple pay, so something else must be happening here
Can you share more details about how you're including this in your UI? Is there anyway to access the underlying frame directly?
we use the payment request button, with react
In the inner frame code, whats the result you're seeing from canMakePayment()? I still think something else is going on. Google Pay not showing showing up suggests this is not directly related to the framing/origin.
Though it could be related if your frame can't communicate and that interferes with the initialization
I would suggest adding some logging around the message receipt and initialization in the inner frame to ensure you're reaching the code paths you expect
You can see an example of this framing cross-origin for the wallets here: https://apocalypse-supplies.glitch.me/apframe
A cool thing made with Glitch
this is framed to another origin, but with static initialization happening there (no cross-origin messages from the parent)