Status Update
No update yet.
Comments
vi...@google.com
We have shared this with our product and engineering team and will update this issue with more information as it becomes available.
na...@gmail.com
POLLEE digital market plece*
Best small bisness marketing by world media with publisher advaisore
Retailler .helsell.small stock. Small buying.curiure world 72 hours world small shoping mall with world publisher .
Order now watts up -8801994343295
Payment. Bikash app -01994343295
Payniore -01994343295
With
POLLEE team organige by green tree green world tree service heppy cleen world publisher jeurny with advaisore world media advisore allways before death working advaisore world media with publisher all ways good working with old porn star helping allways last time life allways 60% old porn poor life with allways all side bed time runing evrybody help line pollee-x teligram with
POLLEE digital market plece *
Payniore -01994343295
vi...@google.com
While our product & engineering team is considering adding a specific wallpaper permission in future releases, this issue has not been prioritized. Starting from version U, the API QUERY_ALL_PACKAGES permission (see the documentation of
lb...@gmail.com
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.
ma...@gmail.com
لايوجد
Description
This is good, and I've reported about it when it wasn't as such:
Thing is, one of the reasons I did it, is because the Play Policy claims that it's possible to use these functions without MANAGE_EXTERNAL_STORAGE. They claim it's possible to do it using MediaStore API, instead.
Today, as I've tried to publish my app, targeting Android 13 and using the new permission, it was denied by the policy team, with the same reason being mentioned.
They claim 2 things which are wrong:
1. Not a core feature. That's despite the fact that the app had this functionality of import&backup of the current wallpaper for a very long time, and it helps with migration from the previous wallpaper to my app (which is a live wallpaper app).
2. App can use MediaStore API to get the current wallpaper. This is also incorrect, and I've shown them the updated documentation about it.
I've already tried to convince them about this for many months already.
I don't want to ruin my app's experience and lose users just because of this.
Currently I can only update the app to use the old READ_EXTERNAL_STORAGE and target Android 12 because of it.
I already told them again and again: If I could use a different permission I would have. I already tried. There is no alternative to it for fetching the current wallpaper. I even requested to have better alternatives on Android 14 for this, once I've found out that Android 13 became a problem:
Please contact the policy team and tell them to stop claiming the wrong things. Make sure they are in-sync because currently they give wrong information to developers and there is nobody else to talk to about it.
There is no other hope, as I'm stuck now in a loop and targeting Android 13 is required soon.