Fixed
Status Update
No update yet.
Comments
ve...@google.com
We have passed this to the development team and will update this issue with more information as it becomes available.
lb...@gmail.com
@2 Thank you. Please hurry about it though. There is a requirement to target Android 13 this year, and still there is no way to convince the Play policy team to let me use the only permission that allows me to use the WallpaperManager API...
ve...@google.com
The issue reported here has been fixed and it will be available in a future release.
lb...@gmail.com
@4 Please explain how it was fixed.
Currently the Play policy is too strict. I can't use MANAGE_EXTERNAL_STORAGE to have this API working, even though this is my only option.
Have you mentioned now on the docs that MANAGE_EXTERNAL_STORAGE is needed on Android 13?
Have you added a new permission on Android 14 or let the alternative storage permissions to have this capability?
Have you talked with Play policy to be less strict about this, as this is currently the only way?
Currently the Play policy is too strict. I can't use MANAGE_EXTERNAL_STORAGE to have this API working, even though this is my only option.
Have you mentioned now on the docs that MANAGE_EXTERNAL_STORAGE is needed on Android 13?
Have you added a new permission on Android 14 or let the alternative storage permissions to have this capability?
Have you talked with Play policy to be less strict about this, as this is currently the only way?
lb...@gmail.com
@4 It seems the docs were updated to mention MANAGE_EXTERNAL_STORAGE, but have you talked with the Play Policy, and you are adding some better alternative for Android 14?
Without this, the API is almost useless, because they are not approving using this API when this permission is declared, unless this is the only feature the app has...
They have an incredibly strict definition of what a "core feature" is, which doesn't let us use API for almost all apps, just because MANAGE_EXTERNAL_STORAGE is required...
Found some issues on the docs, too:
https://issuetracker.google.com/issues/285653479
Without this, the API is almost useless, because they are not approving using this API when this permission is declared, unless this is the only feature the app has...
They have an incredibly strict definition of what a "core feature" is, which doesn't let us use API for almost all apps, just because MANAGE_EXTERNAL_STORAGE is required...
Found some issues on the docs, too:
xt...@live.com
The fix will be only targetting 14?
lb...@gmail.com
@7 Check my comment just above you...
Description
Even worse, it got new functions for Android 14 which still mention only READ_EXTERNAL_STORAGE permission:
This permission can't be granted when targeting Android 13 or 14.
The only possible alternative according to my tests is MANAGE_EXTERNAL_STORAGE.
Please update the documentation, tell what to do on Android 13 and 14, and talk with the privacy policy team to be more flexible in case MANAGE_EXTERNAL_STORAGE permission is the only way to get the wallpaper
Currently the policy team is rejecting all usages of WallpaperManager when MANAGE_EXTERNAL_STORAGE is declared, even though it's the only way to use it when targeting Android 13. This is unfair because there is no other alternative and this API is very simple and harmless, and has existed since the beginning.
It's not our fault that it became something that requires MANAGE_EXTERNAL_STORAGE when all we need is up to 2 images...
Please also consider having a new permission to just get the current wallpapers (images and live wallpaper), and consider letting the READ_MEDIA_IMAGES to be able to do it as well.