Status Update
No update yet.
Comments
ko...@google.com
an...@google.com
ad...@google.com
Missing permissions is a common source of app crashes and related issues. If we can proactively apply best practices when we detect a permission is required, that would be pretty helpful.
Though, it's not clear how we can map the APIs to the required permissions in a scalable, reliable way. We may have to start with the most common APIs and their required permissions.
lb...@gmail.com
@2 How about first scanning of the docs for any mention of permission/s, to see what's missing?
an...@google.com
kd...@google.com
kd...@google.com
an...@google.com
Thank you for your patience while our engineering team worked to resolve this issue. A fix for this issue is now available in:
- Android Studio Meerkat | 2024.3.1 Canary 2
- Android Gradle Plugin 8.9.0-alpha02
We encourage you to try the latest update.
If you notice further issues or have questions, please file a new bug report.
Thank you for taking the time to submit feedback — we really appreciate it!
Description
fun saveFile(context:Context) {
val wallpaperManager = WallpaperManager.getInstance(context)
val test= wallpaperManager.getWallpaperFile(WallpaperManager.FLAG_LOCK)
}
Offer this:
@RequiresPermission(anyOf = [Manifest.permission.READ_EXTERNAL_STORAGE, Manifest.permission.MANAGE_EXTERNAL_STORAGE])