From 541c2e5cac52f6e645d83fd6f97fa348a83d9160 Mon Sep 17 00:00:00 2001
From: twyen <twyen@google.com>
Date: Thu, 10 May 2018 14:54:55 -0700
Subject: 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
---
 java/com/android/dialer/dialpadview/DialpadFragment.java | 7 +------
 1 file changed, 1 insertion(+), 6 deletions(-)

(limited to 'java/com/android/dialer/dialpadview')

diff --git a/java/com/android/dialer/dialpadview/DialpadFragment.java b/java/com/android/dialer/dialpadview/DialpadFragment.java
index d48870dfc..8fb7533f4 100644
--- a/java/com/android/dialer/dialpadview/DialpadFragment.java
+++ b/java/com/android/dialer/dialpadview/DialpadFragment.java
@@ -478,12 +478,7 @@ public class DialpadFragment extends Fragment
     }
     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);
   }
 
   /**
-- 
cgit v1.2.3