Status Update
No update yet.
Comments
sg...@google.com
ch...@google.com
i donnot understand why is the data the same?
a....@gmail.com
ap...@google.com
What steps are needed to reproduce this issue? Frequency of occurrence?
Which Android build are you using? (e.g. AP4A.241205.013.A1)
Which device did you use to reproduce this issue?
Can you confirm if this issue is reproducible on a Pixel/Nexus device?
Please provide a sample project or apk to reproduce the issue. Also mention the steps to be followed for reproducing the issue with the given sample project or apk.
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 bug report and screenshot to google drive and share the folder to android-bugreport@google.com, then share the link here.
ap...@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.
ap...@google.com
for example,we hava 100 users.
20 users returned the same location information, longitude is 121.474000 and latitude is 31.230001。
30 users returned the same location information, longitude is 122.474000 and latitude is 32.230001。
15 users returned the same location information, longitude is 120.474000 and latitude is 30.230001。
as for Android build,all versions have it.
I dont reprodouce this issue.
what may be the cause of this issue?please
ch...@google.com
We have shared this with our product and engineering team and will update this issue with more information as it becomes available.
a....@gmail.com
Thanks for reporting this issue.
COARSE_LOCATION typically takes location information from the nearby cell tower. If many users are near the same cell tower, each of those users will be given the same position. Using a FINE position will give much more detailed information.
Also, in certain areas, for privacy reasons, a less-exact location will be given, and that less-exact location might be identical for many users. Again, a fine-location configuration will return more precise location data.
ch...@google.com
We believe with reference to the above comment, your query has been answered, hence closing the bug. Please feel free to re-open the issue in the future if desired.
ap...@google.com
ap...@google.com
Project: r8
Branch: 8.5
Author: Christoffer Adamsen <
Link:
Limit MissingStartupProfileItemsDiagnostic to 100 items
Expand for full commit details
Limit MissingStartupProfileItemsDiagnostic to 100 items
Bug: b/370937458
Change-Id: I4ef686cac2ee8c7dfe4d09864bb7729017c5e944
Files:
- M
src/main/java/com/android/tools/r8/startup/diagnostic/MissingStartupProfileItemsDiagnostic.java
Hash: 2b742c8fbcdaf8489eea7c29e98694faa4b3b0db
Date: Mon Oct 14 09:56:46 2024
ap...@google.com
Project: r8
Branch: 8.6
Author: Christoffer Adamsen <
Link:
Version 8.6.32
Expand for full commit details
Version 8.6.32
Bug: b/370937458
Change-Id: I6dc835b7b37c6beb70ac21c4ce9db86ed6e298fa
Files:
- M
src/main/java/com/android/tools/r8/Version.java
Hash: bcb1ad58181dd1b9c8af9fa49b4bde12c230e149
Date: Mon Oct 14 09:56:21 2024
ap...@google.com
Project: r8
Branch: 8.6
Author: Christoffer Adamsen <
Link:
Limit MissingStartupProfileItemsDiagnostic to 100 items
Expand for full commit details
Limit MissingStartupProfileItemsDiagnostic to 100 items
Bug: b/370937458
Change-Id: I4ef686cac2ee8c7dfe4d09864bb7729017c5e944
Files:
- M
src/main/java/com/android/tools/r8/startup/diagnostic/MissingStartupProfileItemsDiagnostic.java
Hash: 226e5083b01b2b94abeaf69d0c15b5da6972b757
Date: Mon Oct 14 09:56:11 2024
ap...@google.com
Project: r8
Branch: 8.5
Author: Christoffer Adamsen <
Link:
Limit MissingStartupProfileItemsDiagnostic to 100 items
Expand for full commit details
Limit MissingStartupProfileItemsDiagnostic to 100 items
Bug: b/370937458
Change-Id: I4ef686cac2ee8c7dfe4d09864bb7729017c5e944
Files:
- M
src/main/java/com/android/tools/r8/startup/diagnostic/MissingStartupProfileItemsDiagnostic.java
Hash: 2b742c8fbcdaf8489eea7c29e98694faa4b3b0db
Date: Mon Oct 14 09:56:46 2024
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 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.
Thank you for taking the time to submit feedback — we really appreciate it!
Description
We have a large application with 25 Dex files, so when R8 tries to print diagnostics for missing classes or methods, the Gradle client crashes due to out of memory errors.
The issue is resolved by increasing the maximum heap size using JAVA_OPTS for the Gradle wrapper. I haven't yet investigated the origin of the initial errors since we aren't using a Gradle plugin for startup profile generation. However, they persist even if I delete and then recreate the file using a test.