Change theme
Help
Press space for more information.
Show links for this issue (Shortcut: i, l)
Copy issue ID
Previous Issue (Shortcut: k)
Next Issue (Shortcut: j)
Sign in to use full features.
Vote: I am impacted
Notification menu
Refresh (Shortcut: Shift+r)
Go home (Shortcut: u)
Pending code changes (auto-populated)
View issue level access limits(Press Alt + Right arrow for more information)
Attachment actions
Unintended behavior
View staffing
Description
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: Glance at the code and see that in MainActiviy.kt we are using MediaScannerConnection to index these files
Step #4: With a USB cable plugged in, enable file sharing mode
Step #5: In your desktop file manager, visit the device and its "Internal shared storage" volume
Step #6: Notice that neither test.txt nor QStorage2/test2.txt appear
Step #7: Reboot the device, in hopes that maybe, just maybe, a reboot will trigger a fresh index of external storage, including all files
Step #8: Wait a while after the reboot
Step #9: Repeat steps 4-6 and notice that you have the same results: the files are not visible
Step #10: Repeat steps 2-9 using the qfile app, which is the same app, but with a targetSdkVersion of Q, and notice that you get the same results: the files are not visible
* Issue Category e.g. Framework (platform), NDK (platform), Hardware (CPU, GPU, Sensor, Camera), ART (platform), Runtime Permissions etc
Platform
* What was the expected result?
For the user to somehow be able to get to the files that the app wrote to the root of external storage.
* Can you provide the API document where this expected behavior is explained?
* What was the actual result?
The files do not show up.
Combined with
* Optional: Link to any screenshot(s) that demonstrate the issue (shared privately in Drive.)
Attached is a screenshot showing what we see on a Pixel for the root of external storage. Notice that neither test.txt nor QStorage2/test2.txt appear.