Status Update
No update yet.
Comments
ra...@google.com
ch...@google.com
ch...@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 ed09814db671152793c6f5ca50d19f467acf0943
Author: Christoffer Quist Adamsen <christofferqa@google.com>
Date: Fri Nov 10 10:43:43 2023
Version 8.2.36
Bug:
Change-Id: Icc3b9955aa449ef9d7aa4cb852876fdc22478fbd
M src/main/java/com/android/tools/r8/Version.java
ap...@google.com
Branch: 8.2
commit 530e7269a5f370c70203e3300a2bdfd541fe0466
Author: Christoffer Quist Adamsen <christofferqa@google.com>
Date: Fri Nov 10 10:42:58 2023
Reproduce IllegalAccessError from vertical class merging
Bug:
Change-Id: I4018f662d8261b907d9e1badd322d7c058dd5945
A src/test/java/com/android/tools/r8/classmerging/vertical/InterfaceAccessibleAfterVerticalClassMergingTest.java
A src/test/java/com/android/tools/r8/classmerging/vertical/testclasses/InterfaceAccessibleAfterVerticalClassMergingTestClasses.java
ap...@google.com
Branch: 8.2
commit 7fd1744bf57a76491efd4f09c57b1ef60fed0618
Author: Christoffer Quist Adamsen <christofferqa@google.com>
Date: Fri Nov 10 10:43:08 2023
Fix IllegalAccessError from vertical class merging
Fixes:
Change-Id: If6f4af7f27d93c8145e893d8ac0ab614272a9792
M src/main/java/com/android/tools/r8/shaking/VerticalClassMerger.java
M src/test/java/com/android/tools/r8/classmerging/vertical/InterfaceAccessibleAfterVerticalClassMergingTest.java
an...@airbnb.com
I can confirm that 8.1.73 did fix the issue for us, thank you for the quick fix!
ch...@google.com
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 Hedgehog | 2023.1.1 Patch 1
- Android Gradle Plugin 8.2.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
I attached a processed binary and dump files for the issue.
In there you can see that after R8:
```
package com.airbnb.android.feat.notificationcenter.view;
import com.airbnb.epoxy.i;
import com.airbnb.epoxy.m0;
/* loaded from: classes4.dex */
public final class c implements i {
```
With `com.airbnb.android.feat.notificationcenter.view.c` mapping to `com.airbnb.android.feat.notificationcenter.view.NotificationCenterEpoxyControllerV3$onAttachedToRecyclerView$1`
and `com.airbnb.epoxy.i` mapping to `com.airbnb.epoxy.BaseEpoxyTouchCallback`
`com.airbnb.epoxy.i` is package private and thus cannot be accessed in `com.airbnb.android.feat.notificationcenter.view`, which will lead to a crash.
Originally `c` was extending the public class `com.airbnb.epoxy.EpoxyTouchHelper.SwipeCallbacks` which itself implements the public interface com.airbnb.epoxy.EpoxySwipeCallback` which then extends the package private com.airbnb.epoxy.BaseEpoxyTouchCallback`.
Let me know if I can provide any additional information
------------------
Studio Build: CLI build not relevant
R8 version: 8.1.70 (build 7cf56b7ca0dd612cb0d0cee7e8b806d095a6d4e7 from go/r8bot (luci-r8-custom-ci-focal-8-4dja))
Version of Gradle Plugin: 8.1.1
Version of Gradle: 8.3
Version of Java: OpenJDK 64-Bit Server VM Corretto-17.0.9.8.1 (build 17.0.9+8-LTS, mixed mode, sharing)
OS: Mac OS Sonoma 14.1