Hello @D-Simona-G,

If you try with the theme of the starter does it work?

thanks for your prompt reply!

I did try both with your suggestion and with a freshly built one from the keycloakify-starter repo (without any of my modifications). And it doesn't work, it's the same situation that I showed in my above screenshot.

Forgot to mention my Keycloak server version is 23.0.1

Well then I guess it means that there's a bug in this page.

I didn't implement it myself.

I encourage you to copy over the page to your project and try fixing it, it's usually quite simple since the base Keycloak page are very basic.

If you find the bug you are very wellcome to submit a pull request or report your solution here.

Working on it. If I do manage to fix it I will submit a PR, cheers!

@garronej Sorry for late reply, been quite busy, but I found and fixed the bug on my end. The problem stems from client-side navigation and component lifecycle which was interfering with the correct loading/rendering of the reCaptcha script/widget. E.g., navigating from the the Login page to Register page would result in the widget not rendering, but whilst on Register page, if you'd "hard" refresh the browser or clear cache, it would eventually render. On subsequent refreshes though, it would again not render. This doesn't happen with built-in Keycloak themes for obvious reasons.

Initially, I installed a small package called Reaptcha, to test my theory and that solved all the issues. But figured that some people might not even use reCaptcha feature so adding one more dependency wasn't necessarily justified + it was a bit too much for what was needed imo.
So I ended up using an useEffect hook in the RegisterUserProfile.tsx that manages the reCaptcha script.

If this sounds ok to you, I am happy to create a PR. If so, on which repo should it be?

Hey @D-Simona-G,

Thank you for the thorough explanation. Yes, please create the pull request. While I can't guarantee that I'll merge it as-is, I might need to make some adjustments. In any case, it will be a very valuable reference for people encountering the same issue as you.

I also had a similar issue on the Register page. Using the fix proposed in the PR solved it. Thank you @D-Simona-G

Thanks for reporting @AlexisZankowitch,
The next release will have this fixed

Ref: #538