Status Update
Comments
sg...@google.com <sg...@google.com> #2
i donnot understand why is the data the same?
sg...@google.com <sg...@google.com> #3
sg...@google.com <sg...@google.com> #4
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.
sg...@google.com <sg...@google.com> #5
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 <ap...@google.com> #6
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
ap...@google.com <ap...@google.com> #7
We have shared this with our product and engineering team and will update this issue with more information as it becomes available.
ap...@google.com <ap...@google.com> #8
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.
ap...@google.com <ap...@google.com> #9
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> #10
ap...@google.com <ap...@google.com> #11
Branch: 8.2
commit 62baf24ba2b71f4e5bc04c7f01930bc5d47b02be
Author: Søren Gjesse <sgjesse@google.com>
Date: Thu Jan 11 14:57:48 2024
Version 8.2.47
Bug:
Change-Id: I3398fb8b3b3c04cc470a68721bbdfcc98a2d0b16
M src/main/java/com/android/tools/r8/Version.java
ap...@google.com <ap...@google.com> #12
Branch: 8.3
commit 7301eb962caf2fb63ff2f8d213f7d3483a8a11ec
Author: Søren Gjesse <sgjesse@google.com>
Date: Thu Jan 11 14:56:33 2024
Version 8.3.31
Bug:
Change-Id: I963cb5daf4e2f27d520f9aa8c2172604921e66a5
M src/main/java/com/android/tools/r8/Version.java
ap...@google.com <ap...@google.com> #13
Branch: 8.3
commit 5079ae2cd75dc412a45da0739315b80065bb482e
Author: Søren Gjesse <sgjesse@google.com>
Date: Thu Jan 11 14:56:01 2024
Pass reporter when running BackportedMethodList
Bug:
Change-Id: Iec3beea2ada2ba10aa26d04d9d728e0a672bd7b7
M src/main/java/com/android/tools/r8/BackportedMethodListCommand.java
ap...@google.com <ap...@google.com> #14
Branch: 8.3
commit b6a731f5ddadaf2206217bfa8f37c2ac1a1be2cc
Author: Søren Gjesse <sgjesse@google.com>
Date: Thu Jan 11 14:56:17 2024
Improve the error for unsupported desugared library machine specification
Instead of this message:
Unsupported machine version number 201 not in [200,200]
give the "generic" desugared library error message with DAC references:
Unsupported desugared library configuration version, please upgrade the
D8/R8 compiler.
See
To learn more about library desugaring read
Bug:
Change-Id: I8bfb0f422b601039e10e55c67a8c094671765643
M src/main/java/com/android/tools/r8/ir/desugar/desugaredlibrary/machinespecification/MachineDesugaredLibrarySpecificationParser.java
ap...@google.com <ap...@google.com> #15
Branch: 8.2
commit cff7bfbdbea9d46cec0ffb421f86407f17a8998e
Author: Søren Gjesse <sgjesse@google.com>
Date: Thu Jan 11 14:57:20 2024
Pass reporter when running BackportedMethodList
Bug:
Change-Id: Iec3beea2ada2ba10aa26d04d9d728e0a672bd7b7
M src/main/java/com/android/tools/r8/BackportedMethodListCommand.java
ap...@google.com <ap...@google.com> #16
Branch: 8.2
commit c6c534f1a028d837c1c50a69dbac0104b73f57c2
Author: Søren Gjesse <sgjesse@google.com>
Date: Thu Jan 11 14:57:36 2024
Improve the error for unsupported desugared library machine specification
Instead of this message:
Unsupported machine version number 201 not in [200,200]
give the "generic" desugared library error message with DAC references:
Unsupported desugared library configuration version, please upgrade the
D8/R8 compiler.
See
To learn more about library desugaring read
Bug:
Change-Id: I8bfb0f422b601039e10e55c67a8c094671765643
M src/main/java/com/android/tools/r8/ir/desugar/desugaredlibrary/machinespecification/MachineDesugaredLibrarySpecificationParser.java
sg...@google.com <sg...@google.com> #17
Changes has been merged to Hedgehog/AGP-8.2 Patch 2 and I/AGP-8.3 RC.
an...@google.com <an...@google.com> #18
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 Hedgehog | 2023.1.1 Patch 2
- Android Gradle Plugin 8.2.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!
so...@google.com <so...@google.com> #19
Comment added by automation: A postmortem has been automatically requested for this issue. Please author a postmortem on IRM. See go/android-postmortem-guidance for more context and details, including how to handle the case when this issue does not need a postmortem. If you have any questions not answered by go/android-postmortem-guidance, please email android-hygiene-tpm@, instead of reassigning the fixed bug. Thank you.
an...@google.com <an...@google.com> #20
The fixes for this issue are now also available in:
- Android Studio Iguana | 2023.2.1 RC 1
- Android Gradle Plugin 8.3.0-rc01
We encourage you to try the latest update.
If you notice further issues or have questions, please file a new bug report.
sg...@google.com <sg...@google.com>
cl...@google.com <cl...@google.com> #21
We should try to change the export to machine specification so there's never any conflict instead of adding the merge step of emulated interface descriptor in machine specification. Let's do that before releasing.
Description
With change 85561 the generated machine specification is not longer compatible with previous versions of R8.
Generating
com.android.tools:desugar_jdk_libs_configuration:2.1.0
in96a5fc3f9a34ddc33e4a56861239d813ce9c297b
:With the following diff in the
desugar-jdk-libs
checkout in~/prj/desugar_jdk_libs
:A project using desugared library version 2.1.0 fails Android Studio sync with AGP 8.2.0 with:
Building with
./gradlew :app:assembleRelease
fails the same way:Same for AGP 8.1 and 8.0.