I encountered the problem with chromedriver 121 and above - it looks like Google Chrome 121 introduced changes to its handling of third-party cookies, which could potentially affect how automated tests interact with websites that rely on third-party cookies for various functionalities.
Is there any way to forcefully allow third-party-cookies on the chrome under automated tests ?
approaches in chromeoptions such as args :
--allow-third-party-cookies, --disable-web-security, --disable-site-isolation-trials, --disable-incognito, --no-sandbox,
or prefs:
- 'profile.default_content_setting_values.cookies': 1, 'profile.block_third_party_cookies': false, 'profile.content_settings.exceptions.cookies..setting': 1
are not working - it seems that chrome under test just overrides such security work-arounds