Fixed
Status Update
Comments
hu...@google.com <hu...@google.com>
ey...@gmail.com <ey...@gmail.com> #3
@2 Thank you for the quick handling for this.
I wish policy team of the Play Store could be as cooperative as you guys here.
I wish policy team of the Play Store could be as cooperative as you guys here.
js...@google.com <js...@google.com> #4
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 Giraffe Canary 1 (2022.3.1.1)
- Android Gradle Plugin 8.1.0
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!
js...@google.com <js...@google.com>
an...@google.com <an...@google.com> #5
@4 Seems fixed there.
Can you please check about a similar issue, of various WallpaperManager functions, that the IDE claims I need to have the READ_EXTERNAL_STORAGE even if I target API 33, yet this permission isn't available there:
https://issuetracker.google.com/issues/265579414
?
The policy team is also stuck on the idea that MANAGE_EXTERNAL_STORAGE can't be used for these functions, and according to what I've found, it's actually the opposite: having MANAGE_EXTERNAL_STORAGE granted is the only way to use this functions when targeting&running on Android 13:
https://issuetracker.google.com/issues/237124750#comment44
Please talk to them as I fail to convince them about it, and they won't accept to let me still use these functions on my tiny app.
Can you please check about a similar issue, of various WallpaperManager functions, that the IDE claims I need to have the READ_EXTERNAL_STORAGE even if I target API 33, yet this permission isn't available there:
?
The policy team is also stuck on the idea that MANAGE_EXTERNAL_STORAGE can't be used for these functions, and according to what I've found, it's actually the opposite: having MANAGE_EXTERNAL_STORAGE granted is the only way to use this functions when targeting&running on Android 13:
Please talk to them as I fail to convince them about it, and they won't accept to let me still use these functions on my tiny app.
ey...@gmail.com <ey...@gmail.com> #6
Will this fix make it into 8.7.x?
js...@google.com <js...@google.com> #7
Thanks for the question; I missed the patch 1, but then realized that the patch 2 is due soon. I'll prepare the cherry-pick.
js...@google.com <js...@google.com> #8
^ Done. Will be in 8.7.2
an...@google.com <an...@google.com> #9
The fixes for this issue are now also available in:
- Android Studio Ladybug | 2024.2.1 Patch 2
- Android Gradle Plugin 8.7.2
We encourage you to try the latest update.
If you notice further issues or have questions, please file a new bug report.
du...@gmail.com <du...@gmail.com> #10 Restricted+
Restricted+
ch...@gmail.com <ch...@gmail.com> #11
Comment has been deleted.
Description
DESCRIBE THE ISSUE IN DETAIL:
After updating to 8.7.0 I am getting a false positive RestrictedApi error saying that I cannot call
NavOptionsBuilder.popUpTo
because it is restricted to the library scope.My call:
popUpTo
resolves to:which does not have a
RestrictTo
annotation. There is an overload that does though: