Skip to content

Commit

Permalink
Workaround R8 bug by adding a new proguard rule (#2094)
Browse files Browse the repository at this point in the history
  • Loading branch information
romtsn committed Jun 13, 2022
1 parent a83efb8 commit 2ae42b8
Show file tree
Hide file tree
Showing 2 changed files with 8 additions and 0 deletions.
4 changes: 4 additions & 0 deletions CHANGELOG.md
Expand Up @@ -6,6 +6,10 @@

- Implement local scope by adding overloads to the capture methods that accept a ScopeCallback ([#2084](https://github.com/getsentry/sentry-java/pull/2084))

### Fixes

- Fix proguard rules to work R8 [issue](https://issuetracker.google.com/issues/235733922) around on AGP 7.3.0-betaX and 7.4.0-alphaX ([#2094](https://github.com/getsentry/sentry-java/pull/2094))

## 6.0.0

### Sentry Self-hosted Compatibility
Expand Down
4 changes: 4 additions & 0 deletions sentry-android-core/proguard-rules.pro
Expand Up @@ -11,6 +11,10 @@
-keep class androidx.lifecycle.ProcessLifecycleOwner { <init>(...); }
##---------------End: proguard configuration for androidx.lifecycle ----------

# To mitigate the issue on R8 site (https://issuetracker.google.com/issues/235733922)
# which comes through AGP 7.3.0-betaX and 7.4.0-alphaX
-keepclassmembers enum io.sentry.** { *; }

# don't warn jetbrains annotations
-dontwarn org.jetbrains.annotations.**
# don't warn about missing classes (mainly for Guardsquare's proguard).
Expand Down

0 comments on commit 2ae42b8

Please sign in to comment.