You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+9-2Lines changed: 9 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -192,9 +192,16 @@ Please note that "invisible" simply means that no hCaptcha button will be render
192
192
3.#### Make sure you are using `reCaptchaCompat=false` if you have the reCAPTCHA JS loaded on the same page.
193
193
The hCaptcha "compatibility mode" will interfere with reCAPTCHA, as it adds properties with the same name. If for any reason you are running both hCaptcha and reCAPTCHA in parallel (we recommend only running hCaptcha) then please disable our compatibility mode.
194
194
195
-
4.#### Avoid conflicts with legacy Sentry package usage on react-hcaptcha 1.9.0+
196
-
If you are using Sentry 7.x in your React app, this can conflict with the upstream `hcaptcha-loader` package's Sentry error tracing. You can avoid this issue by setting the `sentry` prop to `false`.
197
195
196
+
### Sentry
197
+
198
+
If the `sentry` flag is enabled, the upstream `hcaptcha-loader` package expects the Sentry SDK, version 8.x or later.
199
+
200
+
If you have an older `@sentry/browser` client version on your site, it may take precedence over the bundled version. In this case you may see a console error like "g.setPropagationContext is not a function" due to the hcaptcha-loader trying to call methods only available on newer Sentry clients.
201
+
202
+
To resolve this, update the version of the Sentry client you are including on your site to 8.x or higher.
203
+
204
+
You can avoid this issue by setting the `sentry` prop to `false`.
0 commit comments