Hesham/wireguard-android
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

build: don't obfuscate code in minify step

Browse Source 
While Play Console correctly manages to deobfuscate stacktraces using the
ProGuard mapping, it makes user recorded logs useless which is rather
undesirable.

Signed-off-by: Harsh Shandilya <me@msfjarvis.dev>
This commit is contained in:
Harsh Shandilya 2020-04-21 21:36:59 +05:30
parent cfb7f1b016
commit 751be2c469
No known key found for this signature in database
GPG Key ID: 366D7BBAD1031E80
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
ui/proguard-rules.pro vendored
View File

@ -2,9 +2,6 @@
# escalates them as errors. # escalates them as errors.
-dontwarn sun.misc.Unsafe -dontwarn sun.misc.Unsafe
# Retain some information to keep stacktraces usable
-keepattributes SourceFile,LineNumberTable
# Fragment 1.2.4 allows Fragment classes to be obfuscated but # Fragment 1.2.4 allows Fragment classes to be obfuscated but
# databinding references in XML seem to not be rewritten to # databinding references in XML seem to not be rewritten to
# match, so we preserve the names as 1.2.3 did. # match, so we preserve the names as 1.2.3 did.
@ -12,3 +9,6 @@
-keep public class <1> { -keep public class <1> {
public <init>(); public <init>();
} }
# Don't obfuscate
-dontobfuscate