Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit 5f6837ff authored by jackqdyulei's avatar jackqdyulei
Browse files

Use FIELD_ANOMALY_TYPE instead of FIELD_CONTEXT

We did it for general anomaly however not the whitelisted one. This
CL fixes it.

Change-Id: I6603ffbaf1d097b360c86406ae0675bfe8a20410
Fixes: 109804858
Test: RunSettingsRoboTests
parent a9b742dd
Loading
Loading
Loading
Loading
+1 −1
Original line number Diff line number Diff line
@@ -157,7 +157,7 @@ public class AnomalyDetectionJobService extends JobService {
                metricsFeatureProvider.action(context,
                        MetricsProto.MetricsEvent.ACTION_ANOMALY_IGNORED,
                        packageName,
                        Pair.create(MetricsProto.MetricsEvent.FIELD_CONTEXT,
                        Pair.create(MetricsProto.MetricsEvent.FIELD_ANOMALY_TYPE,
                                anomalyInfo.anomalyType),
                        Pair.create(MetricsProto.MetricsEvent.FIELD_APP_VERSION_CODE,
                                versionCode));
+1 −1
Original line number Diff line number Diff line
@@ -178,7 +178,7 @@ public class AnomalyDetectionJobServiceTest {
        verify(mFeatureFactory.metricsFeatureProvider).action(mContext,
                MetricsProto.MetricsEvent.ACTION_ANOMALY_IGNORED,
                SYSTEM_PACKAGE,
                Pair.create(MetricsProto.MetricsEvent.FIELD_CONTEXT, ANOMALY_TYPE),
                Pair.create(MetricsProto.MetricsEvent.FIELD_ANOMALY_TYPE, ANOMALY_TYPE),
                Pair.create(MetricsProto.MetricsEvent.FIELD_APP_VERSION_CODE, VERSION_CODE));
    }