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

Yes.

* 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: UnZIP the attached project and import it into Android Studio (tested using 3.4)

Step #2: Run the legacyfile app and confirm that it shows a Toast indicating that files were written -- these will be a test.txt and a QStorage2/test2.txt file in the root of external storage

Step #3: Click the Open Document button to start an ACTION_OPEN_DOCUMENT activity, and notice that neither file shows up when you go to the root of external storage

Step #4: Click the Open Tree button to start an ACTION_OPEN_DOCUMENT_TREE activity, and notice that the QStorage2 directory does not show up when you go to the root of external storage (and wonder why you are seeing files in this activity, but that's a separate problem)

Step #5: Repeat steps 2-4 using the qfile app, which is the same app but with a targetSdkVersion of Q, and notice that you get the same results (nothing that was created shows up in the root of external storage)

Step #6: Use the Files app, navigate

* Issue Category e.g. Framework (platform), NDK (platform), Hardware (CPU, GPU, Sensor, Camera), ART (platform), Runtime Permissions etc

Platform

* What was the expected result?

The files should be visible in the Storage Access Framework UI

* What was the actual result?

The files are not visible, despite the fact that the apps can read them in.

This means that files written by *all* apps to external storage are inaccessible to the user, by any means, unless:

- The app writes them to getExternalFilesDir() and similar locations, or
- The app uses FileProvider and starts third-party activities using a suitable Intent (e.g., ACTION_VIEW)

* Relevant logcat output.

If you happen to select the root of external storage for the Open Tree scenario, Logcat will show a list of the visible contents, and you will get results like:

2019-04-23 16:04:38.206 9778-9778/com.commonsware.android.legacyfile D/Legacy File: # of children = Pictures, Alarms, DCIM, Download, gravatar2.png, Ringtones, Music, Podcasts, Notifications, Movies, Android

Note that neither test.txt nor QStorage2/ show up.

* Optional: Link to any screenshot(s) that demonstrate the issue (shared privately in Drive.)

Attached, please find two screencasts showing the behavior that I describe, for the legacyfile and qfile samples.