When Sentry is enabled, Javascript events seem to be duplicated on third party javascript library (Learnosity)

[lwilson-newclassrooms]

Is there an existing issue for this?

• I have checked for existing issues https://github.com/getsentry/sentry-javascript/issues
• I have reviewed the documentation https://docs.sentry.io/
• I am using the latest SDK release https://github.com/getsentry/sentry-javascript/releases

How do you use Sentry?

Sentry Saas (sentry.io)

Which SDK are you using?

@sentry/react

SDK Version

8.37.1

Framework Version

React 18.3.1

Link to Sentry event

No response

Reproduction Example/SDK Setup

Here is a reproducible app of the issue:

In the README it explains how to run the app and how to reproduce the issue.

https://github.com/lwilson-newclassrooms/sentry-learnosity-repro-app/tree/main

Steps to Reproduce

We created a React app with Vite, integrated a third party javascript library called Learnosity https://learnosity.com/ .

The issue we are experiencing is, when Sentry is enabled, some inputs of Learnosity's forms have a strange behavior.
For example, if you type a '4', the input displays '44'.
When we disable Sentry, Learnosity works as expected, without any issues.

Seems like a conflict between Learnosity and Sentry's javascript keydown events.

The REPRO steps are detailed on the REAMDE of the repo

Expected Result

We expect that Senrtry does not affect the behavior of third party javascript libraries.

Actual Result

The javascript keypress events seem to be duplicated.

[chargome]

hey @lwilson-newclassrooms, thanks for the detailed reproduction! I'll have a look at it today, but as a first step could you try importing Sentry before all other libraries? So in your main.tsx this would be:

import "../sentryInit.ts";
import { createRoot } from "react-dom/client";
import App from "./App.tsx";

createRoot(document.getElementById("root")!).render(<App />);

[lwilson-newclassrooms]

@chargome I tried what you suggested but the issue persists.

[chargome]

@lwilson-newclassrooms unfortunately I was not able to reproduce this behaviour with your repo. I also tried it on different browsers and encountered no issues.

Can you paste your browser+version?

[lwilson-newclassrooms]

@chargome
Chrome Version 130.0.6723.69
Did you tried the input on Item 4 as the README says?
The issue happens when you press on your physical keyboard (not the one displayed on screen).