The public-facing issue tracker URL is issuetracker.google.com. If you visit this URL from a corp account, it will immediately redirect you to the internal-facing issue tracker URL. Make sure that any links you paste publicly have the correct public-facing URL.
The top-level Jetpack component is Android Public Tracker > App Development > Jetpack (androidx).
Issue Tracker isn't a developer support forum. For support information, consider StackOverflow.
Support for Google apps is through Google's support site. Support for third-party apps is provided by the app's developer, for example through the contact information provided on Google Play.
Search for your bug to see if anyone has already reported it. Don't forget to search for all issues, not just open ones, as your issue might already have been reported and closed. To help you find the most popular results, sort the result by number of stars.
If you find your issue and it's important to you, star it! The number of stars on a bug helps us know which bugs are most important to fix.
If no one has reported your bug, file the bug. First, browse for the correct component -- typically this has a 1:1 correspondence with Maven group ID -- and fill out the provided template.
Include as much information in the bug as you can, following the instructions for the bug queue that you‘re targeting. A bug that simply says something isn’t working doesn't help much, and will probably be closed without any action. The amount of detail that you provide, such as a minimal sample project, log files, repro steps, and even a patch set, helps us address your issue.
| Status | Description |
|---|---|
| New | The default for public bugs. Waiting for someone to validate, |
| : : reproduce, or otherwise confirm that this is actionable. : | |
| Assigned | Pending action from the assignee. May be reassigned. |
| Accepted | Actively being worked on by the assignee. Do not reassign. |
| Fixed | Fixed in the development branch. Do not re-open unless the fix is |
| : : reverted. : | |
| WontFix | Covers all the reasons we chose to close the issue without taking |
| : : action (can't repro, working as intended, obsolete). : |
| Priority | Criteria | Resolution time |
|---|---|---|
| P0 | This priority is limited to | Less than 1 day. Don't go home |
| : : service outages, blocking : until this is fixed. : | ||
| : : issues, or other types of work : : | ||
| : : stoppage such as issues on the : : | ||
| : : Platform chase list requiring : : | ||
| : : immediate attention. : : | ||
| P1 | This priority is limited to | Within the next 7 days |
| : : work that requires rapid : : | ||
| : : resolution, but can be dealt : : | ||
| : : with in a slightly longer time : : | ||
| : : window than P0. : : | ||
| P2 | Won't ship without this. | Within the current release |
| P3 | Would rather not ship without | Less than 365 days |
| : : this, but would decide case by : : | ||
| : : case. : : | ||
| P4 | Issue has not yet been | N/A (must triage in under 14 |
| : : prioritized (default as of Feb : days) : | ||
| : : 2013). : : |