Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(5)

Unified Diff: testing/android/proguard_under_test.flags

Issue 2160693002: Turning obfuscation on (Closed) Base URL: https://chromium.googlesource.com/chromium/src.git@annotation
Patch Set: broken Created 4 years, 5 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View side-by-side diff with in-line comments
Download patch
« no previous file with comments | « testing/android/proguard_for_tests.flags ('k') | no next file » | no next file with comments »
Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
Index: testing/android/proguard_under_test.flags
diff --git a/testing/android/proguard_for_test.flags b/testing/android/proguard_under_test.flags
similarity index 86%
rename from testing/android/proguard_for_test.flags
rename to testing/android/proguard_under_test.flags
index f427ac695781a6861f562fd6aefc3ab8612a96df..12714656bf0e43b0bfaffd14131736fdf313e1e0 100644
--- a/testing/android/proguard_for_test.flags
+++ b/testing/android/proguard_under_test.flags
@@ -103,3 +103,11 @@
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
« no previous file with comments | « testing/android/proguard_for_tests.flags ('k') | no next file » | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698