[iPad] The payment detail screen does not appear when click GG pay button

[cloudlyle]

Describe the bug
When not logged into a Google account, clicking the Google Pay button causes the screen to blur and become unresponsive. As shown in the attached video, the only way to regain interaction with the Google Pay button is to open the link in a new tab. Additionally, if the blurred screen disappears and the Google Pay button is clicked again, no action occurs.

To Reproduce
Steps to reproduce the behavior:

1. Open Safari or Chrome on an iPad and Ensure you are logged out of your Google account.
2. Go to https://www.mystoredemo.io/#/checkout.
3. Review the available payment options.
4. Click the Google Pay (GG Pay) button.
5. The login screen for the Google account will appear.
6. Close the Google account login tab and return to the checkout page https://www.mystoredemo.io/#/checkout.

=> Observed Result

• A blurred screen overlay appears, preventing further action.
• When the blurred screen disappears and the Google Pay button is clicked again, there is no response

Expected behavior
When the Google account login screen is closed, the blurred background should clear immediately, allowing the payment details screen to load upon clicking the Google Pay button.

Ipad

• Model: iPad (9th Generation)
• Browser: chrome, safari
• iPadOS Version: 17.7

Video record

RPReplay_Final1731034844.1.1.mp4

[sponglord]

@cloudlyle
I can (partially) recreate this issue on an iPad (OS 18.0), iPhone (17.5.1) & iPhone (18.0)

In all cases Chrome shows the blur/overlay - which doesn't clear.
In Safari the blur/overlay clears after a few seconds and the UI becomes usable again (including the GooglePay button).

I've tested with two different urls, so the issue doesn't lie just with mystoredemo.io

Unfortunately the conclusion I come to is that this is not a problem with Adyen-web or mystoredemo.io.
Rather, it is device/browser specific and so lies outside our control.

If you think otherwise please let us know

[dmengelt]

@cloudlyle / @sponglord We will investigate this from a Google Pay perspective. I will update this issue once I know more...