Infeasible
Status Update
Comments
ra...@google.com <ra...@google.com> #2
When we fix nullability in Jetpack libraries, it is very painful for clients. Also for us attempting to land in g3.
I think this is a good idea; however, I'm not sure if we'd run into any issues since these are currently synthetic annotations generated by Metalava. It's possible that creating real annotations might conflict with the SDK stubs.
Description
####################################################
Please provide all of the following information, otherwise we may not be able to route your bug report.
####################################################
1. Describe the bug or issue that you're seeing.
2. Attach log files from Android Studio
2A. In the IDE, select the Help..Collect Logs and Diagnostic Data menu option.
2B. Create a diagnostic report and save it to your local computer.
2C. Attach the report to this bug using the Add attachments button.
3. If you know what they are, write the steps to reproduce:
3A.
3B.
3C.
In addition to logs, please attach a screenshot or recording that illustrates the problem.
For more information on how to get your bug routed quickly, see
Build: AI-242.23726.103.2422.12816248, 202412180233
AS: Ladybug Feature Drop | 2024.2.2
AI-242.23726.103.2422.12816248, JRE 21.0.4+-12508038-b607.1x64 JetBrains s.r.o., OS Windows 10(amd64) v10.0 , screens 1920x1080 (150%)
Android Gradle Plugin: (plugin information not found)
Gradle: 8.10.2
Gradle JDK: JetBrains Runtime 21.0.4
NDK: from local.properties: (not specified), latest from SDK: (not found)
CMake: from local.properties: (not specified), latest from SDK: (not found), from PATH: (not found)
Source: send_feedback_icon```