Revert null check on dialpadHint
This is caused by apps modifying dialer resources.
TEST=TAP
Bug: 79441501
Test: TAP
PiperOrigin-RevId: 196175830
Change-Id: Ia42e8debe66adbaa2e4e7bdfea7bafe1ef7372bf
diff --git a/java/com/android/dialer/configprovider/SharedPrefConfigProvider.java b/java/com/android/dialer/configprovider/SharedPrefConfigProvider.java
index 54e9c9a..c68312f 100644
--- a/java/com/android/dialer/configprovider/SharedPrefConfigProvider.java
+++ b/java/com/android/dialer/configprovider/SharedPrefConfigProvider.java
@@ -102,6 +102,10 @@
sharedPreferences.edit().putLong(PREF_PREFIX + key, value).apply();
}
+ public void putString(String key, String value) {
+ sharedPreferences.edit().putString(PREF_PREFIX + key, value).apply();
+ }
+
@Override
public String getString(String key, String defaultValue) {
// Reading shared prefs on the main thread is generally safe since a single instance is cached.
diff --git a/java/com/android/dialer/dialpadview/DialpadFragment.java b/java/com/android/dialer/dialpadview/DialpadFragment.java
index d48870d..8fb7533 100644
--- a/java/com/android/dialer/dialpadview/DialpadFragment.java
+++ b/java/com/android/dialer/dialpadview/DialpadFragment.java
@@ -478,12 +478,7 @@
}
digits.setContentDescription(null);
- // TOOD(77908301): Investigate why this is the case
- // It's not clear why digitsHint would be null when digits is initialized as the time, so adding
- // a todo to investigate why.
- if (digitsHint != null) {
- digitsHint.setVisibility(View.GONE);
- }
+ digitsHint.setVisibility(View.GONE);
}
/**