-
-
Save Dema/dcc2b4f91b97ec9d56afc871e66fd3d7 to your computer and use it in GitHub Desktop.
Cypress.Commands.add("clickRecaptcha", () => { | |
cy.window().then(win => { | |
win.document | |
.querySelector("iframe[src*='recaptcha']") | |
.contentDocument.getElementById("recaptcha-token") | |
.click(); | |
}); | |
}); |
-
For reCAPTCHA v2, use the following test key:
const globalSettings: RecaptchaSettings = {siteKey: '6LeIxAcTAAAAAJcZVRqyHh71UMIEGNQ_MXjiZKhI'};
-
In
cypress.config.ts
file setchromeWebSecurity: false
-
Click recaptcha:
cy.get('iframe[src*=recaptcha]')
.its('0.contentDocument')
.should(d => d.getElementById('recaptcha-token').click())
Here's my take (reCAPTCHA v2), which doesn't require waiting:
cy.get('iframe[src*=recaptcha]') .its('0.contentDocument') .should(d => d.getElementById('recaptcha-token').click())
This is interesting. I was able to get it to work as well as the following code here:
cy.get('iframe[src*=recaptcha]').then(($iframe) => {
const iframeDocument = $iframe.contents();
const recaptchaToken = iframeDocument.find('#recaptcha-token');
recaptchaToken.click();
});
However, the next day after a few tests it would not work and was not able to find the #recaptcha-token or the .its() would fail. This is what my team was seeing while reviewing a PR I'd created. I had set up the chromewebsecurity to false and was using the correct test keys provided by Google.
I ended up spending the entire day troubleshooting and trying to figure out what was happening. After a lot of frustrations, I hard reloaded and emptied the cache and now both versions of the click work!!! I have no clue why or what is going on frankly.
I have been trying to bypass the reCaptcha v2 on my system. I tried the above solutions and nothing seems to work.
Can someone please help me with a solution to bypass the image based reCaptcha?
Why are you guys keep asking how to pass automation blocking software using automation software? It is meant to not to be passed like that by design and byt its solely purpose