R8 implicitly replaces an empty member clause with a match of <init>() [323136645]

Fixed

Bug

Status Update

No update yet.

Description

ze...@google.com

created issue #1

Jan 31, 2024 11:26AM

This replacement is wrong for for keepclasseswithmembers as the rule now only applies if the class has a default constructor.

Comments

ap...@google.com <ap...@google.com> #2Feb 1, 2024 08:50AM

for example, many different devices return the same longitude and latitude.such as : longitude is 121.474000 and latitude is 31.230001.
i donnot understand why is the data the same?

ap...@google.com <ap...@google.com> #3Feb 1, 2024 11:32AM

the fractional part of the location data is exactly the same.

ap...@google.com <ap...@google.com> #4Feb 1, 2024 11:32AM

Thank you for reporting this issue. For us to further investigate this issue, please provide the following additional information:

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:

https://developer.android.com/studio/debug/bug-report#bugreportdevice

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.

sh...@gmail.com <sh...@gmail.com> #5Feb 5, 2024 04:28PM

Please provide the requested information to proceed further. Unfortunately the issue will be closed within 7 days if there is no further update.

Screenshot_2024-02-05-07-15-32-08.png

793 KB

View

Download

ch...@google.com <ch...@google.com> May 27, 2024 05:23PM

Reassigned to ch...@google.com.

ap...@google.com <ap...@google.com> #6May 28, 2024 08:25AM

Marked as fixed.

I only aply permission android.permission.ACCESS_COARSE_LOCATION.I use android.location.Location in the program.
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> #7Jul 1, 2024 08:37AM

We have shared this with our product and engineering team and will update this issue with more information as it becomes available.

an...@google.com <an...@google.com> #8Jul 24, 2024 08:39PM

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.