Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error markers not appear in recordings of Clarity platform when native Android application crashes #751

Open
jonathan-juncal opened this issue Jan 28, 2025 · 0 comments
Labels
apps Issues specific to Clarity Apps SDK

Comments

@jonathan-juncal
Copy link

Good afternoon:

I have integrated the Clarity library (version 3.1.2) in a native Android application (SDK 34). In addition to that, I have also integrated the library with Firebase (Analytics and Crashlytics).

Since last week, when forcing errors in development, I am noticing that these errors do not appear marked (only some very occasionally, but barely), in the recordings of the Clarity platform. However, in Crashlytics these errors are reported and also the Clarity link to the corresponding recording where they occurred appears. The question is, what could be happening? It is very curious that the link does appear in Crashlytics with the reported error, but then the marker does not appear... it seems more a failure of the platform than of the code itself.

I hope someone can help me, I am a bit at a dead end, thank you very much.

@ibradwan ibradwan added the apps Issues specific to Clarity Apps SDK label Feb 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
apps Issues specific to Clarity Apps SDK
Projects
None yet
Development

No branches or pull requests

2 participants