IssueTracker

* Which Android Beta build are you using? See Settings > About phone > Build number (for example PPP5.180610.010).
   
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 https://developer.android.com/preview/privacy/scoped-storage#photos-access-location-info where it says "Because this location information is sensitive, Android Q redacts the information by default"

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?

https://developer.android.com/preview/privacy/scoped-storage#photos-access-location-info

    * 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.