lex-web-ui not loading in some Chrome Incognito browsers

[st7788]

We have encountered numerous users not able access the lex-web-ui iFrame component deployed on our site, when they visit the site from an incognito tab on Chrome. This behavior is most prevalent on mobile, however we do occasionally see it on web as well.

This behavior has been encountered by users on different networks, as well as the same network with varying results. There are no CORS errors console errors when this occurs.

[bobpskier]

@st7788 I've tried to reproduce issues using Chrome via mobile device as well as Chrome on OSX and have not been able to reproduce against a site using the IFrame mechanism. What versions of chrome are you using on mobile? Is there a URL you can share that demonstrates the problem?

[st7788]

@bobpskier I was just able to reproduce the issue on Chrome Version 114.0.5735.198, running on OSX. Within the console I get the ChatBotUiLoader loaded message, followed by a timeout error.

I can visit the same URL from the same machine, using non-cognito, and the iFrame component loads with no errors. This behavior has also been observed across multiple networks.

I am working on getting a public URL I can share to demonstrate the problem.

[bobpskier]

@st7788 Usually this timeout means the lex-web-ui-loader-config.json is configured with a parent origin that is different than the origin being used to load the parent page. In the config file check the ui.parentOrigin setting. This must be "https://......" matching exactly the origin of the parent page. Would be helpful if you can share the url.

[st7788]

@bobpskier I have confirmed that the ui.parentOrigin setting and parentOrigin URL in the CloudFront distribution match the origin of the parent page exactly.

The iFrame component and lex-web-ui load in without issue on all devices and networks we have tested, aside from Incognito. I am able to replicate this error repeatedly on Chrome OSX Version 114.0.5735.198, as well as Chrome Android Mobile Version 113.0.5672.162.

I have also tested changing the parentOrigin to multiple different URLs of hosted sites, as well as local hosts, with the same results. Unfortunately I am unable to provide a url at this time.

[bobpskier]

@st7788 I was originally testing using 114.0.5735.198 and could not reproduce against a site that I've deployed. Chrome just updated itself on my system to Version 115.0.5790.114 (Official Build) (arm64) and I still can't reproduce the timeout while loading. Can you point your system to https://lander.tioth.com and let me know if you can reproduce? Any sort of plugins in play on Chrome that might be influencing loading an iframe?

[Judge40]

@bobpskier I'm experiencing this same problem with my own site, I've just tested against https://lander.tioth.com and get the same time out error when using Incognito.

Chrome Version: 115.0.5790.110 (Official Build) (64-bit)
OS: Windows 10

I can reproduce the same issue on https://lander.tioth.com using Chrome (114.0.5735.227) in Incognito on an Android device.
Both devices work as expected when not using Incognito mode.