Bug P3
Status Update
Comments
ku...@gmail.com <ku...@gmail.com> #2
Do you have a repro project that you could share with us?
There should be no need to excluding any dependencies: we automatically remove them from the test APK if they are in the main APK.
There should be no need to excluding any dependencies: we automatically remove them from the test APK if they are in the main APK.
vi...@google.com <vi...@google.com>
vi...@google.com <vi...@google.com> #3
Thank you for reporting this issue. For us to further investigate this issue, please provide the following additional information:
Device used -- Device Make, Model, Android OS Version
Which device did you use to reproduce this issue?
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.
Expected output
What is the expected output?
Current output
What is the current output?
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 Record of the Issue
Please capture screen record or video of the issue using following steps:
adb shell screenrecord /sdcard/video.mp4
Subsequently use following command to pull the recorded file:
adb pull /sdcard/video.mp4
Attach the file to this issue.
Note: Please upload the bug report and screenshot to google drive and share the folder to android-bugreport@google.com, then share the link here.
Device used -- Device Make, Model, Android OS Version
Which device did you use to reproduce this issue?
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.
Expected output
What is the expected output?
Current output
What is the current output?
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 Record of the Issue
Please capture screen record or video of the issue using following steps:
adb shell screenrecord /sdcard/video.mp4
Subsequently use following command to pull the recorded file:
adb pull /sdcard/video.mp4
Attach the file to this issue.
Note: Please upload the bug report and screenshot to google drive and share the folder to android-bugreport@google.com, then share the link here.
sa...@gmail.com <sa...@gmail.com> #4
Devices used: Pixel 2 XL API 29, LG G6 API 26
Sample project is trivial, description is in the first bug report.
Expected output: also in the first report. The test should just pass.
Actual output: stacktrace is in the first report.
Screen recording: the bug is about Integration tests. Nothing happens on screen.
vi...@google.com <vi...@google.com>
bo...@google.com <bo...@google.com> #5
Please let us know if there is any update on this bug.
ae...@google.com <ae...@google.com> #6
This bug has not been updated in the last year. Please reopen if we still need to look into this.
Description
I'm trying to write instrumented tests for a DocumentProvider using ProviderTestRule to replace ProviderTestCase2, but it keeps throwing a SecurityException.
Steps to reproduce:
Module build.gradle:
Expected behavior: the test passes normally.
Actual behavior: