Assigned
Status Update
Comments
ke...@google.com <ke...@google.com>
jb...@google.com <jb...@google.com>
co...@google.com <co...@google.com> #2
Please attach a sample project that reproduces your issue.
jo...@google.com <jo...@google.com> #3
co...@google.com <co...@google.com>
ni...@regainapp.ai <ni...@regainapp.ai> #4
Project: platform/frameworks/support
Branch: androidx-master-dev
commit bd065925676170c8453321e970d455fac06b8d3d
Author: Ian Lake <ilake@google.com>
Date: Mon Jan 28 15:47:16 2019
Add ProGuard rules for DrawerArrowDrawable.setProgress()
setProgress() is called via an ObjectAnimator and
therefore needs to be specifically kept when
obfuscating with ProGuard.
Test: tested in sample project attached to bug
Change-Id: I9c420ce728c5cb887d29df9f856bfd31f5bdbcdf
Fixes: 123449431
M navigation/ui/build.gradle
A navigation/ui/proguard-rules.pro
https://android-review.googlesource.com/887876
https://goto.google.com/android-sha1/bd065925676170c8453321e970d455fac06b8d3d
Branch: androidx-master-dev
commit bd065925676170c8453321e970d455fac06b8d3d
Author: Ian Lake <ilake@google.com>
Date: Mon Jan 28 15:47:16 2019
Add ProGuard rules for DrawerArrowDrawable.setProgress()
setProgress() is called via an ObjectAnimator and
therefore needs to be specifically kept when
obfuscating with ProGuard.
Test: tested in sample project attached to bug
Change-Id: I9c420ce728c5cb887d29df9f856bfd31f5bdbcdf
Fixes: 123449431
M navigation/ui/build.gradle
A navigation/ui/proguard-rules.pro
ni...@regainapp.ai <ni...@regainapp.ai> #5
We've added the appropriate ProGuard configuration and it'll be available in the next release.
As a workaround, you can add the following to your ProGuard configuration:
-keepclassmembers class android.support.v7.graphics.drawable.DrawerArrowDrawable {
void setProgress(float);
}
As a workaround, you can add the following to your ProGuard configuration:
-keepclassmembers class android.support.v7.graphics.drawable.DrawerArrowDrawable {
void setProgress(float);
}
Description
1.7.2
1.7.2
material-navigation:1.7.0-beta01
1.9.23
We're observing random crashes within
BottomSheetNavigator
when user tries to press (we assume) system back. Unfortunately we do not have any repro steps for now as it happens to margin of users, without any clear distinction for Android version / manufacturer.The stack trace points to
retainedEntry!!
usage, which in turn seems like a race condition:I know the same issue has been already reported about it back when this code was within accompanist library, linking those here:
Stack trace (if applicable):