microsoft / clarity-apps

Repo for distributing Clarity Apps packages
MIT License
46 stars 2 forks source link

Not able to see all the recorded session. #15

Closed bipulbafna closed 11 months ago

bipulbafna commented 1 year ago

I'm using react-native-clarity sdk with version 4.0.0 because latest version 5.0.0 was not working in my react native app, build gets failed. With 4.0.0 I'm able to initailise the sdk also able to see the recorded session. But when I try initialising in the emulator mostly it shows the recorded sessions in the clarity dashboard but when I create release apk and try the app, it won't show the recorded session most of the time. How can we fix this? Please help.

Animesh-UMR commented 1 year ago

Facing similar issue.

ibradwan commented 1 year ago

Hi there, In order to help us debug these issues, kindly share with us the following:

  1. Share the details of the build failure you are facing with 0.0.5.
  2. Share the logs from a release build s.t. we can figure out the root cause. You can enable the logs by setting the log level to "Verbose" while initializing Clarity.
khanh21011999 commented 11 months ago

Hi @ibradwan , i have question about the logLevel What is this for, i try to set logLevel = LogLevel by all these value Verbose = "Verbose", Debug = "Debug", Info = "Info", Warning = "Warning", Error = "Error", None = "None"

But it not different anything in the recording, my task is to display more information like network and other things in recording, how can i do that ?

ibradwan commented 11 months ago

@khanh21011999 Thanks for reaching out.

Loglevel is an SDK configuration that allows you to see the SDK logs in the device logcat stream. When you enable these logs, you'll be able to diagnose any issues that you might have with the SDK (like when your sessions are not showing up on the dashboard).

Currently the only way to add extra data to a session is by using custom tags, where you provide key-value pairs, and they should show up on the dashboard.

khanh21011999 commented 11 months ago

Thank for reply @ibradwan , i have one concern is how can i access these log? I do not see it anywhere in console and another problem is when i setup the userId by const clarityConfig = { userId:"abcd" }; And put it in the init, then i see the abcd is the customId instead of id One more thing is, can we have more info in the recording tab, like api call etc.. in recording tab?

Screenshot 2023-12-26 at 22 19 38

And version 2.1 support ios also, right ?

ibradwan commented 10 months ago

They should be in the device logcat stream, you can view these logs by running: adb logcat -s "Clarity". Note that unlike the console.log(); logs, the Clarity logs won't show up in the ReactNative console.

The userId has a set of constraints. If you pass an invalid user id it will be populated in the CustomUserId field, and a random user id will be generated for the session.

Regarding adding more events to the recordings page, we do have plans to support richer events like network ones, so please stay tuned for future releases.

Currently our ReactNative SDK only works on Android, but we are actively working on bringing the iOS support soon.

khushalsonawat commented 8 months ago

I can see the recording on the dashboard but all I see is a blank screen. This is the log content of the adb logcat -s "Clarity" command. Any clue why this might be happening?

react-native-clarity version : 2.1.0

03-20 12:52:58.688  7213  7213 I Clarity : <packageName>.MainActivity@<id> is resumed.
03-20 12:52:58.688  7213  7213 D Clarity : Watch touches for <packageName>.MainActivity@<id>.
03-20 12:52:58.689  7213  7213 D Clarity : [SourceFile::invoke] Register setting window callback task for <packageName>.MainActivity@<id>.
03-20 12:52:58.690  7213  7213 D Clarity : [SourceFile::invoke] Register frame capture task for <packageName>.MainActivity@<id>.
03-20 12:52:58.692  7213  7997 D Clarity : Queue size: 0.
03-20 12:52:58.692  7213  7997 D Clarity : Enqueuing analytics event Visibility task received for activity MainActivity#116363154.
03-20 12:52:58.693  7213  7996 D Clarity : Task queue size: 0.
03-20 12:52:58.693  7213  7996 D Clarity : [SourceFile::invoke] New analytics event Visibility received for activity MainActivity#116363154.
03-20 12:52:58.693  7213  7996 D Clarity : [SourceFile::invoke] Dropping Analytics Event because current page payload count limit has been exceeded
03-20 12:52:58.957  7213  7213 D Clarity : [SourceFile::invoke] Capture frame for <packageName>.MainActivity@<id>.
03-20 12:52:58.957  7213  7213 D Clarity : [SourceFile::invoke] Frame timestamp: 1710919378957.
03-20 12:52:58.957  7213  7213 D Clarity : [SourceFile::invoke] Frame shouldMaskCurrentActivity: false.
03-20 12:52:58.989  7213  7997 D Clarity : Queue size: 0.
03-20 12:53:12.490  7213  7213 I Clarity : Touch event watched ([1710919392489,19,0,851,1098]).
03-20 12:53:12.497  7213  7213 I Clarity : Touch event watched ([1710919392496,19,0,851,1109]).
03-20 12:53:12.512  7213  7213 I Clarity : Touch event watched ([1710919392512,19,0,851,1122]).
03-20 12:53:12.529  7213  7213 I Clarity : Touch event watched ([1710919392529,19,0,851,1132]).
03-20 12:53:12.541  7213  7213 I Clarity : Touch event watched ([1710919392541,19,0,850,1132]).
03-20 12:53:12.544  7213  7213 I Clarity : Touch event watched ([1710919392543,18,0,850,1132]).
.
.
.
.
.
03-20 12:53:27.804  7213  7996 D Clarity : [SourceFile::invoke] Dropping Analytics Event because current page payload count limit has been exceeded
03-20 12:53:28.038  7213  8044 I Clarity : [SourceFile::invoke] Report metric worker started.
03-20 12:53:28.040  7213  8044 D Clarity : --> POST https://www.clarity.ms/report/project/kla0f9i15f/metrics.
03-20 12:53:28.040  7213  8044 D Clarity : [SourceFile::a] --> https://www.clarity.ms/report/project/kla0f9i15f/metrics: [{"v":"2.1.1","n":"Clarity_UIThreadWork","c":83,"s":1890,"min":0,"max":118,"stdev":38.05206493493046,"f":1},{"v":"2.1.1","n":"Clarity_CaptureFrame","c":27,"s":1824,"min":25,"max":116,"stdev":35.39024068585109,"f":1},{"v":"2.1.1","n":"Clarity_TotalFrameDuration","c":447,"s":9536,"min":9,"max":287,"stdev":20.117959373065556,"f":1}].
03-20 12:53:28.529  7213  8044 D Clarity : [SourceFile::a] <-- https://www.clarity.ms/report/project/kla0f9i15f/metrics: 200 OK.
03-20 12:53:37.072  7213  7213 I Clarity : <packageName>.MainActivity@<id> is resumed.
03-20 12:53:37.072  7213  7213 D Clarity : Watch touches for <packageName>.MainActivity@<id>.
03-20 12:53:37.073  7213  7213 D Clarity : [SourceFile::invoke] Register setting window callback task for <packageName>.MainActivity@<id>.
03-20 12:53:37.074  7213  7213 D Clarity : [SourceFile::invoke] Register frame capture task for <packageName>.MainActivity@<id>.
03-20 12:53:37.075  7213  7997 D Clarity : Queue size: 0.
03-20 12:53:37.075  7213  7997 D Clarity : Enqueuing analytics event Visibility task received for activity MainActivity#116363154.
03-20 12:53:37.076  7213  7996 D Clarity : Task queue size: 0.
03-20 12:53:37.076  7213  7996 D Clarity : [SourceFile::invoke] New analytics event Visibility received for activity MainActivity#116363154.
03-20 12:53:37.076  7213  7996 D Clarity : [SourceFile::invoke] Dropping Analytics Event because current page payload count limit has been exceeded
03-20 12:53:37.246  7213  7213 D Clarity : [SourceFile::invoke] Capture frame for <packageName>.MainActivity@<id>.
03-20 12:53:37.247  7213  7213 D Clarity : [SourceFile::invoke] Frame timestamp: 1710919417247.
03-20 12:53:37.247  7213  7213 D Clarity : [SourceFile::invoke] Frame shouldMaskCurrentActivity: false.
03-20 12:53:37.284  7213  7997 D Clarity : Queue size: 0.
03-20 12:53:37.905  7213  7997 D Clarity : [SourceFile::a] Mask picture for MainActivity#116363154 with maskRestrictively: false.
.
.
.
.

03-20 12:53:37.907  7213  7997 D Clarity : Enqueuing display frame task for activity MainActivity#116363154.
03-20 12:53:37.907  7213  7996 D Clarity : Task queue size: 0.
03-20 12:53:41.757  7213  7996 D Clarity : [SourceFile::invoke] New frame received for activity MainActivity#116363154.
03-20 12:53:41.757  7213  7996 D Clarity : [SourceFile::invoke] Dropping Display Frame because current page payload count has been exceeded
03-20 12:53:41.862  7213  8001 I Clarity : [SourceFile::invoke] Report metric worker started.
03-20 12:53:41.865  7213  8001 D Clarity : --> POST https://www.clarity.ms/report/project/kla0f9i15f/metrics.
03-20 12:53:41.865  7213  8001 D Clarity : [SourceFile::a] --> https://www.clarity.ms/report/project/kla0f9i15f/metrics: [{"v":"2.1.1","n":"Clarity_UIThreadWork","c":12,"s":253,"min":0,"max":67,"stdev":25.29643694717148,"f":1},{"v":"2.1.1","n":"Clarity_CaptureFrame","c":5,"s":239,"min":30,"max":66,"stdev":14.204224723651764,"f":1},{"v":"2.1.1","n":"Clarity_TotalFrameDuration","c":75,"s":1884,"min":12,"max":231,"stdev":31.271695402285648,"f":1}].

Thanks

ibradwan commented 8 months ago

Hello @khanh21011999,

I've just checked and it seems like your project has sessions already. Please note that you can see live sessions while the users are interacting with your application, then those sessions will take around 1 hour to show up in the regular sessions list.