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
diff --git a/java/com/android/dialer/callintent/CallIntentBuilder.java b/java/com/android/dialer/callintent/CallIntentBuilder.java
index 87de0f0..b5b680e 100644
--- a/java/com/android/dialer/callintent/CallIntentBuilder.java
+++ b/java/com/android/dialer/callintent/CallIntentBuilder.java
@@ -68,6 +68,7 @@
.setTimeSinceFirstClick(PerformanceReport.getTimeSinceFirstClick())
.addAllUiActionsSinceAppLaunch(PerformanceReport.getActions())
.addAllUiActionTimestampsSinceAppLaunch(PerformanceReport.getActionTimestamps())
+ .setStartingTabIndex(PerformanceReport.getStartingTabIndex())
.build();
PerformanceReport.stopRecording();
}