Status Update
No update yet.
Comments
an...@google.com
an...@google.com
Thank you for reporting this issue.For us to further investigate this issue, please provide the following additional information:
Could you please explain the issue a bit more in detail?
What steps would let us observe this issue?
What did you expect to happen?
What actually happened?
Android bug report (to be captured after reproducing the issue) For steps to capture a bug report, please refer:
Alternate method Navigate to “Developer options”, ensure “USB debugging” is enabled, then enable “Bug report shortcut”. Capture bug report by holding the power button and selecting the “Take bug report” option.
Note: Please upload the files to google drive and share the folder to
an...@google.com
Please provide the requested information to proceed further. Unfortunately the issue will be closed within 7 days if there is no further update.
an...@google.com
We're closing this issue due to not having enough actionable information. If you continue to have this issue, please file a new issue and add the relevant information along with a reference link to the earlier issue.
Description
This form is only for reporting app issues found when running on Android 16 Developer Preview or Beta builds. Only report app issues that are regressions from the behavior in Android 15. For all other issues that are also reproducible on other versions of Android, please report those issues in the AOSP issue tracker athttps://goo.gl/TbMiIO .
If the issue is not due to a platform bug, we will do our best to notify the developer of the app. However, note that it is up to the developer to actually address reported issues.
Before logging your issue, check to see whether it is a known issue described in the current release notes at:
or has already been reported at:
If the issue has already been reported, you can "star" or comment on the existing report if it corresponds to the issue you are seeing.
To expedite resolution of your issue, please provide as much relevant and specific information as possible. This will probably require some work from you. Most reports should include at least the following:
Are you an Android developer?" (Y/N)
Which Android Developer Preview or Betabuild are you using? See Settings > About phone > Build number (for example AP3A.241105.008).
Is this a regression from Android 15 to 16?
What device are you using? (for example, Android Emulator, GSI, Pixel 9)
App Package Name?
What are the steps to reproduce the problem? (Please provide the minimal reproducible test case.)
What was the expected result?
What was the actual result?
Relevant logcat output
Link to captured Android bug report (shared privately in Drive.)
Optional: Link to any screenshot(s) that demonstrate the issue (shared privately in Drive)
To avoid the possibility of sharing private information, please share bugreports and screenshots from Google Drive. Share files withandroid-bugreport@google.com and include only Google drive links in your bug. Please note, bug report attachments should not be included directly in issue reports.
Disclaimer: Please note, by submitting this bug report, you acknowledge that Google may use information included in the bug report to diagnose technical issues and to improve our products and services, in accordance with our Privacy Policy (https://policies.google.com/privacy ), and you agree that we may share it with engineering partners potentially impacted by your issue.
Bug reports include personal information logged on your device or by apps, such as: File names Installed apps and usage Email addresses of the profiles on the device Device identifiers, such as phone number Web history information, including URLs / URIs Location information, including limited location history Network information, such as IP/SSID/MAC addresses and saved or scanned APNs System or device information, such as memory and processes