* 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: From the command line, run adb shell ls /storage/emulated/0, and notice that the test.txt and QStorage2/test2.txt files are not visible

Step #4: From the command line, run adb shell run-as com.commonsware.android.legacyfile ls /storage/emulated/0, and notice that the test.txt and QStorage2/test2.txt files are not visible

(feel free to repeat with the qfile project and com.commonsware.android.qfile to see the same results)

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

Platform

* What was the expected result?

One or both of those commands to show the files.

* What was the actual result?

The files do not show up.

This problem is less critical than either https://issuetracker.google.com/issues/131170877 or https://issuetracker.google.com/issues/131154410, as one or both of those simply have to get fixed. However, while fixing those, if you could allow adb access (particularly to help the Device File Explorer in Android Studio), that would be very helpful.