Turning obfuscation on

testing/android/proguard_under_test.flags

 # Copyright 2016 The Chromium Authors. All rights reserved.
 # Use of this source code is governed by a BSD-style license that can be
 # found in the LICENSE file.
 
 # This file is for proguard flags which will be applied to apks that are being
 # built to be instrumentation tested. The flags in this file should only affect
 # how the instrumentation tests interact with the .apk. Do not put any flags in
 # this file which might affect the correctness of the .apk.
 
 # This line prevents optmization from being applied to either packages. We rely
@@ skipping 85 matching lines @@
 # Needed for chrome_sync_shell_test_apk. Note - these do no affect chrome_apk's
 # size.
 -keep class org.chromium.sync.protocol.* { *; }
 
 # These resources are referenced in tests, but not in the real application.
 -keepclassmembers class org.chromium.chrome.R$id {
   int webapp_splash_space;
   int mr_chooser_list;
   int find_toolbar;
 }
+
+# This is to prevent renaming two methods in two different interfaces to the
+# same name. The testing .apk has a few classes which implement two interfaces
+# that are never implemented together in the real .apk, and thus would create a
+# conflict. We don't expect the absence of this to cause any issues in the real
+# .apk, since the same classes are still being obfuscated, and the ProGuarded
+# .apk is not then being fed into another run.
+-useuniqueclassmembernames