Use timestamp to track policy state + store it in a local state pref as opposed to a file.
1. Replace use of file to store the latest uploaded crash timestamp with a local state pref.
2. Use the timestamp to track enabled state of crash event reporting policy state. A timestamp of 0 means that the feature was previously not enabled, and enabling it would set the earliest crash time to be reported as the current time.
Bug: b/270571190
Change-Id: I226ecada15a7f097d5e62f900b2db38d864d16db
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4290129
Commit-Queue: Nasser Al-shawwa <[email protected]>
Reviewed-by: Avi Drissman <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1111691}
diff --git a/chrome/browser/prefs/browser_prefs.cc b/chrome/browser/prefs/browser_prefs.cc
index 9dbc2e5..437a821 100644
--- a/chrome/browser/prefs/browser_prefs.cc
+++ b/chrome/browser/prefs/browser_prefs.cc
@@ -1161,6 +1161,7 @@
registry->RegisterIntegerPref(first_run::kTosDialogBehavior, 0);
registry->RegisterBooleanPref(lens::kLensCameraAssistedSearchEnabled, true);
#else // BUILDFLAG(IS_ANDROID)
+ enterprise_connectors::RegisterLocalStatePrefs(registry);
gcm::RegisterPrefs(registry);
headless::RegisterPrefs(registry);
IntranetRedirectDetector::RegisterPrefs(registry);
