Status Update
No update yet.
Comments
do...@gmail.com
i donnot understand why is the data the same?
mk...@google.com
do...@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.
cl...@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.
do...@gmail.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
cl...@google.com
We have shared this with our product and engineering team and will update this issue with more information as it becomes available.
cl...@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.
do...@gmail.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
do...@gmail.com
I tried the patch and the issue has been fixed. Could it be backported to 8.1 or 8.0?
ap...@google.com
Branch: 8.1
commit e0e551933215b00b4f58e16ecaa471260b576a97
Author: Christoffer Quist Adamsen <christofferqa@google.com>
Date: Mon Jul 31 09:44:49 2023
Prevent Outlining from generating methods with > 255 args
Bug:
Change-Id: I40148a493edb50a3f9220d990a5b4fb05158e97d
M src/main/java/com/android/tools/r8/ir/optimize/outliner/OutlinerImpl.java
A src/test/java/com/android/tools/r8/ir/optimize/outliner/OutlineInvokeStaticBailoutTest.java
ap...@google.com
Branch: 8.1
commit d5dd9e6bb336bbd63c2596ae74c6125139902d46
Author: Christoffer Quist Adamsen <christofferqa@google.com>
Date: Mon Jul 31 09:47:06 2023
Version 8.1.60
Bug:
Change-Id: I3051af4969df3d6203ad3c64ae55d7985aa3240c
M src/main/java/com/android/tools/r8/Version.java
ap...@google.com
Branch: 8.0
commit 55e3bbcc638e7f7ac5fc19865bd73e061aa1e547
Author: Christoffer Quist Adamsen <christofferqa@google.com>
Date: Mon Jul 31 10:16:33 2023
Version 8.0.58
Bug:
Change-Id: I698cc433de48219d05f64648b4dfe6004750c9b2
M src/main/java/com/android/tools/r8/Version.java
ap...@google.com
Branch: 8.0
commit 8f7663bcd206626b2dd01f8022e52d803495531f
Author: Christoffer Quist Adamsen <christofferqa@google.com>
Date: Mon Jul 31 10:16:20 2023
Prevent Outlining from generating methods with > 255 args
Bug:
Change-Id: I40148a493edb50a3f9220d990a5b4fb05158e97d
M src/main/java/com/android/tools/r8/ir/optimize/OutlinerImpl.java
A src/test/java/com/android/tools/r8/ir/optimize/outliner/OutlineInvokeStaticBailoutTest.java
do...@gmail.com
8.0.58 & 8.1.60 fix my issue. thx!
cl...@google.com
ap...@google.com
Branch: 8.1
commit a8407fb98d10b2a7d6499000741ceb5659bc3ff8
Author: Søren Gjesse <sgjesse@google.com>
Date: Wed Aug 16 11:16:22 2023
Version 8.1.65
Bug:
Bug:
Change-Id: Ic88eb9a81dcea0651390088696c32760acd1814d
M src/main/java/com/android/tools/r8/Version.java
ap...@google.com
Branch: 8.1
commit fbaccf38bc0b1484f416cda5bf52503dbe20116d
Author: Søren Gjesse <sgjesse@google.com>
Date: Wed Aug 16 11:14:37 2023
Revert "Prevent Outlining from generating methods with > 255 args"
This reverts commit e0e551933215b00b4f58e16ecaa471260b576a97.
Bug:
Bug:
Change-Id: I5ce9d4a6e805a957630c64671ae43bab803467aa
M src/main/java/com/android/tools/r8/ir/optimize/outliner/OutlinerImpl.java
D src/test/java/com/android/tools/r8/ir/optimize/outliner/OutlineInvokeStaticBailoutTest.java
do...@gmail.com
I'm curious why revert this commit on 8.1?
sg...@google.com
We received this report
The issue in
Description
We changed
getDefaultProguardFile('proguard-android.txt')->getDefaultProguardFile('proguard-android-optimize.txt')and app crash
debug apk without r8 bytecode is like:
release apk with r8 optimize bytecode is like:
mapping is like: