Fixed
Status Update
Comments
mm...@commonsware.com <mm...@commonsware.com> #2
Thank you for reporting this issue. For us to further investigate this issue, please go over the data below carefully and provide the following additional information:
- Android Build Version (go to Settings > About Device > Build Number (hold down to copy))
- Android Device Model:
- Please provide a sample project by uploading the exported zip file of the project from Android Studio or a sample apk file. 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.
- Upload the bug report file. Steps followed here:https://developer.android.com/studio/debug/bug-report 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.
- Steps taken for issue to occur:
1.
2.
3.
etc...
- Expected output: What is the expected output?
- Current output: What is the current output?
Thank you for your cooperation.
- Android Build Version (go to Settings > About Device > Build Number (hold down to copy))
- Android Device Model:
- Please provide a sample project by uploading the exported zip file of the project from Android Studio or a sample apk file. 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.
- Upload the bug report file. Steps followed here:
- Steps taken for issue to occur:
1.
2.
3.
etc...
- Expected output: What is the expected output?
- Current output: What is the current output?
Thank you for your cooperation.
ve...@google.com <ve...@google.com>
ve...@google.com <ve...@google.com> #3
- Android Build Version: ONEPLUS A5010_43_200513 / Android 10.0.0
The issue has been reported an open source project which use the WEB_URL
pattern.
https://github.com/signalapp/Signal-Android/issues/9449 https://github.com/signalapp/Signal-Android/issues/9122
I've also noticed the problem in Telegram, and SMS messenger services.
mm...@commonsware.com <mm...@commonsware.com> #4
We’ve shared this with our product and engineering teams and will continue to provide updates as more information becomes available.
mm...@commonsware.com <mm...@commonsware.com> #5
En español
ar...@google.com <ar...@google.com> #6
Would you accept a patch for this issue?
ad...@google.com <ad...@google.com>
ji...@google.com <ji...@google.com> #7
Happy birthday to this bug! Are you happy to accept a patch for this?
Description
google/sailfish/sailfish:Q/QPP2.190228.023/5433927:user/release-keys
* Is this a regression from P to Q?
No, this is new behavior 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 #1: Read
Step #2: Copy the attached JPEG of the Statue of Liberty to external storage on the device
Step #3: UnZIP the attached project, import it into Android Studio (tested on 3.4), and run it
Step #4: Notice that the UI of the app is showing a photo of Freedom Tower in NYC, and it shows the EXIF data from this image (copied out of assets into getExternalFilesDir())
Step #5: Click the "image" toolbar button and navigate through the Storage Access Framework UI to find the Statue of Liberty image that you copied in Step #2, and select it
Step #6: Notice that the UI of the app is now showing a photo of the Statue of Liberty, and it shows the EXIF data from this image
* Issue Category e.g. Framework (platform), NDK (platform), Hardware (CPU, GPU, Sensor, Camera), ART (platform), Runtime Permissions etc
Either framework or documentation
* What was the expected result?
For the EXIF data to be redacted, per the documentation.
* Can you provide the API document where this expected behavior is explained?
* What was the actual result?
The EXIF data was not redacted, so we can use ExifInterface to get the EXIF data.
It is unclear if the problem is in the EXIF redaction logic or in the documentation. For the latter, if EXIF redaction only affects certain scenarios, that should be covered in the documentation.