microsoft/clarity

Uncaught TypeError: Cannot read properties of undefined (reading 'latency')

Closed this issue · 9 comments

tachev commented

Describe the bug
Recently (today) in the console I see a lot of errors. I see thoese captured in Clarity as well (no pun intended)

clarity.js:2 Uncaught TypeError: Cannot read properties of undefined (reading 'latency')
at ao (clarity.js:2:63408)
at clarity.js:2:64910
at PerformanceObserver.co (clarity.js:2:65051)
at PerformanceObserver. (clarity.js:2:58987)

Repro Steps
Reproducing it is easy, any page that has the clarity code shows that on loading.

Project info
https://tangra.link/images

Browser info:
Chrome version 130.0.6723.92

lvinno commented

We met the similar issue in our project. Wondering is it newly introduced? As we also only observed this issue starting from today.

  • 👍9
shtbik commented

Upvote!

  • 👍6
tachev commented

Seems it's related with the UET tag from MS Ads. Not sure yet, but there seems to be some conflict with it. If I remove Clarity from the tag, another error started:
0.7.52:1 Uncaught TypeError: (void 0) is not a function
at ze (0.7.52:1:23696)
at Pe (0.7.52:1:23639)
at 0.7.52:1:33023
at Xe.u.onreadystatechange (0.7.52:1:22755)

If I remove the whole tag altogether and leave only Clarity I don't see the error

eyupucmaz commented

We had the same issue in our projects. We were using vite plugin and thought the plugin was un-updated. Then start to use the Clarity script. It's seems still we have this issue.

  • 👍1
eyupucmaz commented

I think it's solved with this PR #696

Stuj1 commented

I think it's solved with this PR #696

Great, any ideas when we can expect the fixed script to be available?

  • 👍3
AbdelrhmanMagdy commented

Thanks for reporting this issue, this is now fixed in the latest version.

  • 👍2
  • 🎉2
tachev commented

Thanks for reporting this issue, this is now fixed in the latest version.

WOW! That was fast! Thanks a lot!

tachev commented

Thanks for reporting this issue, this is now fixed in the latest version.

It doesn't happen so often, but still I get errors:
0.7.53:1 Uncaught TypeError: (void 0) is not a function
at ze (0.7.53:1:23696)
at Pe (0.7.53:1:23639)
at 0.7.53:1:33023
at Xe.u.onreadystatechange (0.7.53:1:22755)