WAI
Status Update
Comments
mm...@commonsware.com <mm...@commonsware.com> #2
Sorry, forgot to attach the project and a relevant screenshot.
ku...@google.com <ku...@google.com>
ku...@google.com <ku...@google.com> #3
Thank you for reporting this issue. For us to further investigate this issue, please provide the following additional information:
Screen record of the issue, for clarity
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 files to google drive and share the folder to android-bugreport@google.com, then share the link here.
Screen record of the issue, for clarity
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 files to google drive and share the folder to android-bugreport@google.com, then share the link here.
mm...@commonsware.com <mm...@commonsware.com> #4
Attached is a screencast of the instructions from this issue.
ku...@google.com <ku...@google.com> #5
Thank you for reporting this issue. We have shared this with our product and engineering team and will update this issue with more information as it becomes available.
mm...@commonsware.com <mm...@commonsware.com> #6
This can be reproduced on Q Beta 3 (google/sailfish/sailfish:10/QPP3.190404.015/5505587:user/release-keys) running on a Pixel.
mm...@commonsware.com <mm...@commonsware.com> #7
This can be reproduced on Q Beta 4:
[ro.vendor.build.fingerprint]: [google/sailfish/sailfish:10/QPP4.190502.018/5616371:user/release-keys]
[ro.vendor.build.fingerprint]: [google/sailfish/sailfish:10/QPP4.190502.018/5616371:user/release-keys]
mm...@commonsware.com <mm...@commonsware.com> #8
This can be reproduced on Q Beta 5:
[ro.vendor.build.fingerprint]: [google/sailfish/sailfish:10/QPP5.190530.014/5691763:user/release-keys]
[ro.vendor.build.fingerprint]: [google/sailfish/sailfish:10/QPP5.190530.014/5691763:user/release-keys]
ku...@google.com <ku...@google.com> #9
Response from engineering team:
==========================================
This is WAI. We support content uris only.
==========================================
This is WAI. We support content uris only.
Description
[ro.vendor.build.fingerprint]: [google/sailfish/sailfish:Q/QPP2.190228.023/5433927:user/release-keys]
* Is this a regression from P to Q?
No, this is new functionality to Q
* What device are you using? (for example, Pixel XL)
Pixel
* What are the steps to reproduce the problem? (Please provide the minimal reproducible test case.)
Step #0: Prep your test device to have some content on external storage, including at least one icon-sized image file and one MP4 video
Step #1: UnZIP the attached project, import it into Android Studio (tested on 3.3.2), and run it
Step #2: Click the fourth button ("Share content, content preview")
Step #3: From the Storage Access Framework UI, pick the image from Step #0 -- you should see a share sheet with the image serving as the preview
Step #4: Click the third button ("Share content, resource preview")
* Issue Category e.g. Framework (platform), NDK (platform), Hardware (CPU, GPU, Sensor, Camera), ART (platform), Runtime Permissions etc
???
* What was the expected result?
To see a preview area in the share sheet with "This is the preview title" and the image from res/drawable/ic_child_care_black_24dp.xml.
* What was the actual result?
The preview area just has "This is the preview title", with no image.
The difference in the two code paths is that the one that works uses the selected image, while the one that does not work uses an android.resource:// Uri pointing to the drawable resource. The preview should work with any valid Uri.