From e75840fe4dfc77ad28ed6ffca7f37202e272c00a Mon Sep 17 00:00:00 2001 From: Colin Cross Date: Thu, 11 Apr 2019 14:09:37 -0700 Subject: [PATCH] Add default proguard flags from guava Guava 27.1 causes some warnings in R8, silence them. Bug: 130306229 Test: m checkbuild Change-Id: Ia9948d597538a16c5b7ab26a2e41eebde52e7427 Merged-In: Ia9948d597538a16c5b7ab26a2e41eebde52e7427 Exempt-From-Owner-Approval: cherry pick (cherry picked from commit b4917146aa3b7de6e23aff2834871837067cffeb) --- core/proguard_basic_keeps.flags | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/core/proguard_basic_keeps.flags b/core/proguard_basic_keeps.flags index 3c25e895fa..256b2ecb79 100644 --- a/core/proguard_basic_keeps.flags +++ b/core/proguard_basic_keeps.flags @@ -66,5 +66,12 @@ # See bug/20658265. # -dontwarn android.support.** +# From https://github.com/google/guava/wiki/UsingProGuardWithGuava +# Striped64, LittleEndianByteArray, UnsignedBytes, AbstractFuture +-dontwarn sun.misc.Unsafe +# Futures.getChecked (which often won't work with Proguard anyway) uses this. It +# has a fallback, but again, don't use Futures.getChecked on Android regardless. +-dontwarn java.lang.ClassValue + # Less spammy. -dontnote