Assigned
Status Update
Comments
su...@google.com <su...@google.com>
su...@google.com <su...@google.com> #2
We have shared this with our product and engineering team and will update this issue with more information as it becomes available.
ka...@gmail.com <ka...@gmail.com> #3
Good Morning,
Please could I have assistance with my device is been hacked and sensitive personal and business information was leaked . My banking details and emails been exposed.
My media files been deleted remotely. Please assist me with this issue its been going on for couple months but I nought a new device thi king it would stop now I see it's happening again.
Please could I have assistance with my device is been hacked and sensitive personal and business information was leaked . My banking details and emails been exposed.
My media files been deleted remotely. Please assist me with this issue its been going on for couple months but I nought a new device thi king it would stop now I see it's happening again.
ra...@google.com <ra...@google.com>
lb...@gmail.com <lb...@gmail.com> #4
I've even provided a presentation, a video, and a sample to prove the policy team they are wrong for my app (LWP+) that it indeed does require MANAGE_EXTERNAL_STORAGE permission and none of what they said is true, that it's not a core feature and that I can do it using MediaStore API or SAF API.
See attached file here.
See attached file here.
co...@gmail.com <co...@gmail.com> #5
Thank you
co...@gmail.com <co...@gmail.com> #6
Thank you
Description
I didn't mention getWallpaperInfo anywhere there.
Also, this is incorrect or at least not documented anywhere :
"Apps that seek to process the current wallpaper image should prompt the user to select the wallpaper image from their media storage."
No Intent exists to let the user choose the current wallpaper of lock/home-screen, so that the app could fetch it without any kind of permission.
The only way to get the current wallpaper is by using WallpaperManager :
The issue here is about MANAGE_EXTERNAL_STORAGE permission. This permission is required when targeting Android 13. There is no way to avoid it.
Please talk with the policy team so that you will both be in sync about this matter.
Only this way they will be flexible about having this permission for this purpose, as a minimized permission isn't available yet.