From 26f520249eccdcf2352806ba8d6a54bb8e5045a6 Mon Sep 17 00:00:00 2001 From: zachh Date: Fri, 26 Jan 2018 16:28:44 -0800 Subject: Reworked the internals of DialerPhoneNumber. It turns out the storing the libphonenumber representation of the number is not particularly useful because even formatting these objects cannot be done on the main thread. Rather than propagate the requirement of using PhoneNumberUtil (and background threads by extension) in the call log UI, we now just store a dialer-normalized version of the number which contains all information required by the UI in a way that allows us to avoid any background work in the UI code. Bug: 72563861 Test: existing PiperOrigin-RevId: 183463907 Change-Id: I4bdadaccb7a84033b3c72c54fe3833064f587ee3 --- java/com/android/dialer/phonelookup/composite/CompositePhoneLookup.java | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'java/com/android/dialer/phonelookup') diff --git a/java/com/android/dialer/phonelookup/composite/CompositePhoneLookup.java b/java/com/android/dialer/phonelookup/composite/CompositePhoneLookup.java index 622b4db10..b77a86ca0 100644 --- a/java/com/android/dialer/phonelookup/composite/CompositePhoneLookup.java +++ b/java/com/android/dialer/phonelookup/composite/CompositePhoneLookup.java @@ -133,7 +133,7 @@ public final class CompositePhoneLookup implements PhoneLookup if (subInfo == null) { throw new IllegalStateException( "A sublookup didn't return an info for number: " - + LogUtil.sanitizePhoneNumber(dialerPhoneNumber.getRawInput().getNumber())); + + LogUtil.sanitizePhoneNumber(dialerPhoneNumber.getNormalizedNumber())); } phoneLookups.get(i).setSubMessage(combinedInfo, subInfo); } -- cgit v1.2.3