From 9cbf3ce9c73eca62a8b45d7b4e35135e7d476fef Mon Sep 17 00:00:00 2001 From: yueg Date: Wed, 23 Aug 2017 15:47:51 -0700 Subject: Fix starting_tab_index not set bug. starting_tab_index should be set in CallSpecificAppData in the constructor of CallIntentBuilder, and then logged in CallEvent. However the first step was not done before this change. Test: LoggerUtilsTest PiperOrigin-RevId: 166266818 Change-Id: I3904371e34551c9ef89ea9622cb35b9517d16e7f --- java/com/android/dialer/callintent/CallIntentBuilder.java | 1 + 1 file changed, 1 insertion(+) (limited to 'java') diff --git a/java/com/android/dialer/callintent/CallIntentBuilder.java b/java/com/android/dialer/callintent/CallIntentBuilder.java index 87de0f0ec..b5b680e48 100644 --- a/java/com/android/dialer/callintent/CallIntentBuilder.java +++ b/java/com/android/dialer/callintent/CallIntentBuilder.java @@ -68,6 +68,7 @@ public class CallIntentBuilder { .setTimeSinceFirstClick(PerformanceReport.getTimeSinceFirstClick()) .addAllUiActionsSinceAppLaunch(PerformanceReport.getActions()) .addAllUiActionTimestampsSinceAppLaunch(PerformanceReport.getActionTimestamps()) + .setStartingTabIndex(PerformanceReport.getStartingTabIndex()) .build(); PerformanceReport.stopRecording(); } -- cgit v1.2.3