Duplicate spans in Sentry

[rlinoz]

https://expensify.sentry.io/explore/traces/trace/048f51066eac49a2876f814b05310da6/?end=2025-12-12T11%3A33%3A00&environment=production&fov=0%2C15136.39990234375&node=span-b12df236f2c4196d&pageEnd=2025-12-12T11%3A33%3A00.000&pageStart=2025-12-12T10%3A58%3A00.000&query=user.email%3A%EF%80%8DContains%EF%80%8Dexpensify%40growthlabfinancial.com&source=traces&start=2025-12-12T10%3A58%3A00&targetId=a8061c14dde797e1&timestamp=1765538422&utc=true

We often see duplicate spans in Sentry, which makes it harder to investigate what is going on and also each span that we send cost us money, so having them duplicate can be expensive.

Let's find out why and fix it.

[sosek108]

Problem is only for browsers and is due to the fact that we enable browserTracingIntegration alongside with reactNativeTracingIntegration

http://github.com/Expensify/App/blob/03921a5810308c80d625fc758e7b5e6cd3afec60/src/libs/telemetry/integrations.ts#L19

[sosek108]

Here is Draft PR where I remove browserTracingIntegration.

I've added this with browserProfilingIntegration when we've been enabling tracing for browser. I don't remember exactly why this was added

[sosek108]

PR was merged 2 days ago. And currently I'm noticing drop of ~50% http releated spans for simillar days (Sat, Sun). I've not been able to find any duplicated span.

Seems to be working 🚀

[rlinoz]

Nice job!

[rlinoz]

Deployed to prod and it is workign!