Status Update
No update yet.
Comments
dr...@gmail.com
i donnot understand why is the data the same?
dr...@gmail.com
ze...@google.com
dr...@gmail.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.
ze...@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.
ze...@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 4c60fbcbcee7d387e6effb8426cec27a61a9e785
Author: Ian Zerny <zerny@google.com>
Date: Tue Aug 22 09:32:25 2023
Regression and fix for trivial-phi issue in field get removal
Bug:
Change-Id: Ifca4c63f1a9a1dd3291abd7d27deb06fba929a7c
M src/main/java/com/android/tools/r8/ir/optimize/RedundantFieldLoadAndStoreElimination.java
A src/test/java/com/android/tools/r8/ir/optimize/redundantfieldloadelimination/RedundantFieldLoadEliminationTrivialPhiTest.java
ap...@google.com
Branch: 4.0
commit d36bdedf23f4089aab81b857047726e6fb264fee
Author: Ian Zerny <zerny@google.com>
Date: Mon Aug 21 15:30:49 2023
Regression and fix for trivial-phi issue in field get removal
Bug:
Change-Id: Ifca4c63f1a9a1dd3291abd7d27deb06fba929a7c
M src/main/java/com/android/tools/r8/ir/optimize/RedundantFieldLoadAndStoreElimination.java
A src/test/java/com/android/tools/r8/ir/optimize/redundantfieldloadelimination/RedundantFieldLoadEliminationTrivialPhiTest.java
ap...@google.com
Branch: 4.0
commit 434d7229079692f7c844a966e4488583652afcd0
Author: Ian Zerny <zerny@google.com>
Date: Mon Aug 21 15:31:02 2023
Version 4.0.68
Bug:
Change-Id: If57a8daddb6705e267d92e29052e55b0d8df3324
M src/main/java/com/android/tools/r8/Version.java
ap...@google.com
Branch: 8.0
commit 32b14e9bf44e8be586a2bd360b0ee10a0c8d721b
Author: Ian Zerny <zerny@google.com>
Date: Mon Aug 21 15:38:51 2023
Regression and fix for trivial-phi issue in field get removal
Bug:
Change-Id: Ifca4c63f1a9a1dd3291abd7d27deb06fba929a7c
M src/main/java/com/android/tools/r8/ir/optimize/RedundantFieldLoadAndStoreElimination.java
A src/test/java/com/android/tools/r8/ir/optimize/redundantfieldloadelimination/RedundantFieldLoadEliminationTrivialPhiTest.java
ap...@google.com
Branch: 8.0
commit d64ab925c6e287ca1c7a3fbb16621429ac76c22b
Author: Ian Zerny <zerny@google.com>
Date: Mon Aug 21 15:39:23 2023
Version 8.0.63
Bug:
Change-Id: I848de6da54c737314fb7014a8205bf9f689bbf7a
M src/main/java/com/android/tools/r8/Version.java
ap...@google.com
Branch: 8.1
commit f4774aee4dd52f42a2a79e7197fcf7a91e61b081
Author: Ian Zerny <zerny@google.com>
Date: Tue Aug 22 08:48:52 2023
Regression and fix for trivial-phi issue in field get removal
Bug:
Change-Id: Ifca4c63f1a9a1dd3291abd7d27deb06fba929a7c
M src/main/java/com/android/tools/r8/ir/optimize/RedundantFieldLoadAndStoreElimination.java
A src/test/java/com/android/tools/r8/ir/optimize/redundantfieldloadelimination/RedundantFieldLoadEliminationTrivialPhiTest.java
ap...@google.com
Branch: 4.0
commit d36bdedf23f4089aab81b857047726e6fb264fee
Author: Ian Zerny <zerny@google.com>
Date: Mon Aug 21 15:30:49 2023
Regression and fix for trivial-phi issue in field get removal
Bug:
Change-Id: Ifca4c63f1a9a1dd3291abd7d27deb06fba929a7c
M src/main/java/com/android/tools/r8/ir/optimize/RedundantFieldLoadAndStoreElimination.java
A src/test/java/com/android/tools/r8/ir/optimize/redundantfieldloadelimination/RedundantFieldLoadEliminationTrivialPhiTest.java
ap...@google.com
Branch: 8.0
commit 32b14e9bf44e8be586a2bd360b0ee10a0c8d721b
Author: Ian Zerny <zerny@google.com>
Date: Mon Aug 21 15:38:51 2023
Regression and fix for trivial-phi issue in field get removal
Bug:
Change-Id: Ifca4c63f1a9a1dd3291abd7d27deb06fba929a7c
M src/main/java/com/android/tools/r8/ir/optimize/RedundantFieldLoadAndStoreElimination.java
A src/test/java/com/android/tools/r8/ir/optimize/redundantfieldloadelimination/RedundantFieldLoadEliminationTrivialPhiTest.java
ze...@google.com
Thanks again for reporting this issue and for the reproduction. A fix has landed on each of the R8 release branches, so you can update your config to the version suitable for your AGP release. Let us know if any issues remain.
dr...@gmail.com
I can confirm that both build time error and run time VerifyError is fixed on API 21 and API 33 emulators, with tag 8.3.2-dev which includes the fix:
repositories {
...
maven {
url = uri("https://storage.googleapis.com/r8-releases/raw")
}
}
dependencies {
classpath 'com.android.tools:r8:8.3.2-dev'
...
}
Do you know when this fix will make it into a stable release?
ze...@google.com
The fix did not make it for the AGP 8.1.1 point release, so it would first be included if another point release is made. It will be the stable release of 8.2 when that is cut.
ze...@google.com
Also, the fix is on the R8 release branches so you can use the one that matches your AGP instead of using our -dev branch which is not very stable.
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 Giraffe | 2022.3.1 Patch 2
- Android Gradle Plugin 8.1.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!
sx...@gmail.com
It seems to me that this variant is more acceptable, but I am not completely sure to argue it
Description
Error:
Steps to reproduce:
git revert 1ae5a81to stop disabling R8 full mode.signing.propertiesby followingsigning.properties.examplein the project, i.e. generate a signing key and fill it in../gradlew clean build.Note that I have tried deleting my gradle cache (
$HOME/.gradle/), but the issue persisted even after the cache is cleared.