Skip to content

Commit

Permalink
Abstract proguard rules at package level (#1247)
Browse files Browse the repository at this point in the history
  • Loading branch information
thePeras authored Jun 25, 2024
2 parents dac5a02 + abbe72b commit 5775214
Showing 1 changed file with 10 additions and 7 deletions.
17 changes: 10 additions & 7 deletions uni/android/app/proguard-rules.pro
Original file line number Diff line number Diff line change
Expand Up @@ -20,10 +20,13 @@
# hide the original source file name.
#-renamesourcefileattribute SourceFile

# The 6 lines below are added to fix #1243
-dontwarn com.google.errorprone.annotations.CanIgnoreReturnValue
-dontwarn com.google.errorprone.annotations.CheckReturnValue
-dontwarn com.google.errorprone.annotations.Immutable
-dontwarn com.google.errorprone.annotations.RestrictedApi
-dontwarn javax.annotation.Nullable
-dontwarn javax.annotation.concurrent.GuardedBy
# These are annotations related to static analysis tools. Proguard
# tries to optimize/obfuscate the bundle, it needs all
# packages to be present. Because these annotations do not exist
# at optimize time, it will warn us that it cannot find those packages.
# Unfortunaly, AFAIK there's no real way to packages include their "own"
# proguard or some of them just do not do it, so we sometimes need to handle it
# when we add a new dependency.

-dontwarn com.google.errorprone.annotations.*
-dontwarn javax.annotation.*

0 comments on commit 5775214

Please sign in to comment.