Set IS_PENDING for files created via filePath
Previously, we didn't set IS_PENDING for files created via filePath.
When is_pending is not set, apps consider those files as published and
ready to read, which leads to displaying partial/corrupted files or
computing wrong SHA for files etc. In order to avoid these, we should
hide these files created via file path by setting IS_PENDING=1. As
there is no reliable way to know when the file is ready to be
published, we consider all files created via file path as
non-publishable until the next scan.
Changed insertFileForFuse to set IS_PENDING for files created via
filePath. Unlike explicitly set pending files, pending files from FUSE
will be visible to other apps for filePath operations. IS_PENDING will
be unset when the app explicitly inserts the row to db or when the media
scanner scans the corresponding file.
For MediaProvider APIs there will be no difference between explicitly
set IS_PENDING and IS_PENDING set by FUSE.
Test: atest CtsScopedStorageHostTest
Bug: 157171910
Change-Id: If3e075d072fe5c05889e05d595eac70902263c5b
10 files changed