Fixed
Status Update
Comments
b9...@gmail.com <b9...@gmail.com> #2
Any news on this issue?
da...@google.com <da...@google.com> #3
Thank you for reporting this issue. For us to further investigate this issue, please provide the following additional information:
Android build
Which Android build are you using? (e.g. OPP1.170223.012)
Device used
Which device did you use to reproduce this issue?
Steps to reproduce
What steps are needed to reproduce this issue?
Frequency
How frequently does this issue occur? (e.g 100% of the time, 10% of the time)
Android bug report (to be captured after reproducing the issue)
For steps to capture a bug report, please refer:https://developer.android.com/studio/debug/bug-report#bugreportdevice
Alternate method
Navigate to “Developer options”, ensure “USB debugging” is enabled, then enable “Bug report shortcut”. Capture bug report by holding the power button and selecting the “Take bug report” option.
Screen capture of the issue
Press the volume down and power buttons simultaneously. The image will appear in your gallery. Attach the screenshot file to this issue.
Note: Please upload the files to google drive and share the folder to android-bugreport@google.com, then share the link here.
Android build
Which Android build are you using? (e.g. OPP1.170223.012)
Device used
Which device did you use to reproduce this issue?
Steps to reproduce
What steps are needed to reproduce this issue?
Frequency
How frequently does this issue occur? (e.g 100% of the time, 10% of the time)
Android bug report (to be captured after reproducing the issue)
For steps to capture a bug report, please refer:
Alternate method
Navigate to “Developer options”, ensure “USB debugging” is enabled, then enable “Bug report shortcut”. Capture bug report by holding the power button and selecting the “Take bug report” option.
Screen capture of the issue
Press the volume down and power buttons simultaneously. The image will appear in your gallery. Attach the screenshot file to this issue.
Note: Please upload the files to google drive and share the folder to android-bugreport@google.com, then share the link here.
b9...@gmail.com <b9...@gmail.com> #4
Please share the details requested in comment #3 , to proceed further with the bug.
da...@google.com <da...@google.com> #5
Android build:
Happened on every Android version I tested this, i.e. API 21 to API 29
Device used:
Pixel 2 XL as well as several emulated devices in Android Studio
Steps to reproduce:
See original post
Frequency:
Always, i.e. 100%
Android bug report:
N.A.
Screen capture of the issue
N.A.
Happened on every Android version I tested this, i.e. API 21 to API 29
Device used:
Pixel 2 XL as well as several emulated devices in Android Studio
Steps to reproduce:
See original post
Frequency:
Always, i.e. 100%
Android bug report:
N.A.
Screen capture of the issue
N.A.
b9...@gmail.com <b9...@gmail.com> #6
Facing the same problem. UsageStatsManager.queryUsageStats seems to return unpredictable results. I will post more details later.
da...@google.com <da...@google.com> #7
Please provide sample project or apk to reproduce the issue. Also mention the steps to be followed for reproducing the issue with the given sample project or apk.
Description
The Data Binding Library supports resources in binding expressions, and drawable resources in particular.
<ImageView
android:layout_width="match_parent"
android:layout_height="match_parent"
android:src="@{condition ? @drawable/image1 : @drawable/image2}" />
But if your project uses support vector drawables you're in a big trouble.
android {
defaultConfig {
vectorDrawables.useSupportLibrary = true
}
}
Unfortunately, the Data Binding Library doesn't call AppCompatResources.getDrawable() when loading drawables, so the binding above will throw an exception at runtime on pre-Lollipop devices.
See details: