Why are steps and respective screenshots sometimes assigned to the wrong screenviews in mobile app session replay?
-
Out of order steps and screenshots may occur when screenview controllers, activities, or fragments are loaded into one another. This can be resolved by disabling the capture of the child control(s) in the TealeafLayoutConfig.json file. Below is an example of a disabled screen view.
"ChildViewController": {
"ScreenChange": false,
"DisplayName": "Child Screen View",
"CaptureLayoutDelay": 0,
"ScreenShot": false,
"NumberOfWebViews": 0,
"CaptureUserEvents": false,
"CaptureScreenVisits": false,
"CaptureLayoutOn": 0,
"CaptureScreenshotOn": 0
},For more TealeafLayoutConfig.json examples, refer to the following article:
https://developer.goacoustic.com/acoustic-exp-analytics/docs/configuring-the-acoustic-tealeaf-sdk-for-ios#4-enable-type-10-screen-logging-for-native-mobile-applications-by-using-the-autolayout-controller
Please sign in to leave a comment.
Comments
1 comment