Status Update
No update yet.
Comments
ap...@google.com
i donnot understand why is the data the same?
ap...@google.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
ap...@google.com
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
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
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
Branch: 8.2
commit f407251acb3b760cd10defc37218e73ad401bd4f
Author: Ian Zerny <zerny@google.com>
Date: Mon Apr 22 09:56:15 2024
Register all referencing contexts for API stubs
Bug:
Change-Id: Iac464d7beaea858444777323d09ad7f1ee44d290
M src/main/java/com/android/tools/r8/androidapi/ApiReferenceStubber.java
A src/test/java/com/android/tools/r8/synthesis/globals/GlobalSyntheticStubContextRegressionTest.java
ap...@google.com
Branch: 8.3
commit acd8441900910a91f55150373dfc0eaa45d5e990
Author: Ian Zerny <zerny@google.com>
Date: Mon Apr 22 09:46:09 2024
Register all referencing contexts for API stubs
Bug:
Change-Id: Iac464d7beaea858444777323d09ad7f1ee44d290
M src/main/java/com/android/tools/r8/androidapi/ApiReferenceStubber.java
A src/test/java/com/android/tools/r8/synthesis/globals/GlobalSyntheticStubContextRegressionTest.java
ap...@google.com
Branch: 8.1
commit 78a7e914b2cfda67c8b32e70ca71d0640ce4b30f
Author: Ian Zerny <zerny@google.com>
Date: Mon Apr 22 09:58:07 2024
Register all referencing contexts for API stubs
Bug:
Change-Id: Iac464d7beaea858444777323d09ad7f1ee44d290
M src/main/java/com/android/tools/r8/androidapi/ApiReferenceStubber.java
A src/test/java/com/android/tools/r8/synthesis/globals/GlobalSyntheticStubContextRegressionTest.java
ap...@google.com
Branch: 8.2
commit f407251acb3b760cd10defc37218e73ad401bd4f
Author: Ian Zerny <zerny@google.com>
Date: Mon Apr 22 09:56:15 2024
Register all referencing contexts for API stubs
Bug:
Change-Id: Iac464d7beaea858444777323d09ad7f1ee44d290
M src/main/java/com/android/tools/r8/androidapi/ApiReferenceStubber.java
A src/test/java/com/android/tools/r8/synthesis/globals/GlobalSyntheticStubContextRegressionTest.java
ze...@google.com
ap...@google.com
Branch: 8.1
commit 78a7e914b2cfda67c8b32e70ca71d0640ce4b30f
Author: Ian Zerny <zerny@google.com>
Date: Mon Apr 22 09:58:07 2024
Register all referencing contexts for API stubs
Bug:
Change-Id: Iac464d7beaea858444777323d09ad7f1ee44d290
M src/main/java/com/android/tools/r8/androidapi/ApiReferenceStubber.java
A src/test/java/com/android/tools/r8/synthesis/globals/GlobalSyntheticStubContextRegressionTest.java
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 Jellyfish | 2023.3.1 Patch 1
- Android Gradle Plugin 8.4.1
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
The registration of contexts when creating global stub types is computed behind a seen-types cache. Thus only the initial generating context is registered. The result of this is that an incremental build may be incomplete if this initial generating context is changed to no long need the global which some other context still uses it and was not part of the compilation unit.
This issue can manifest as a verification error when an Exception type stub is missing on the target device.