Status Update
Comments
vs...@google.com <vs...@google.com>
je...@google.com <je...@google.com>
be...@google.com <be...@google.com> #2
i donnot understand why is the data the same?
cm...@google.com <cm...@google.com> #3
lu...@google.com <lu...@google.com> #4
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.
de...@google.com <de...@google.com> #5
Please provide the requested information to proceed further. Unfortunately the issue will be closed within 7 days if there is no further update.
lu...@google.com <lu...@google.com> #6
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
cm...@google.com <cm...@google.com> #7
We have shared this with our product and engineering team and will update this issue with more information as it becomes available.
lu...@google.com <lu...@google.com> #8
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.
an...@google.com <an...@google.com> #9
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.
mi...@swiftkey.com <mi...@swiftkey.com> #10
th...@opera.com <th...@opera.com> #11
(Please, could you at least verify fixes?)
xa...@google.com <xa...@google.com>
lu...@google.com <lu...@google.com>
lu...@google.com <lu...@google.com> #12
Thanks for reporting the issue, unfortunately this wasn't caught when manually testing the original fix; the project in comment 10 reproduces the issue.
There is a fix and regression test merged to the main branch (8.4-alpha08). This will be cherry-picked to AGP 8.3 and 8.2 (expected in 8.2.3)
jr...@squareup.com <jr...@squareup.com> #13
lu...@google.com <lu...@google.com> #14
Marking as fixed, as the fix is merged at head and for 8.3; still waiting on cherry-pick merge for 8.2, I'll update this issue when merged to 8.2.
an...@google.com <an...@google.com> #15
Further fixes for this issue are now available in:
- Android Studio Iguana | 2023.2.1 RC 1
- Android Gradle Plugin 8.3.0-rc01
We encourage you to try the latest update.
If you notice further issues or have questions, please file a new bug report.
an...@google.com <an...@google.com> #16
The fixes for this issue are now also available in:
- Android Studio Jellyfish | 2023.3.1 Canary 8
- Android Gradle Plugin 8.4.0-alpha08
We encourage you to try the latest update.
If you notice further issues or have questions, please file a new bug report.
th...@opera.com <th...@opera.com> #17
do...@traveloka.com <do...@traveloka.com> #18
8.2.x will be fixed or not?
ka...@gmail.com <ka...@gmail.com> #19
Thank you
ro...@ebay.com <ro...@ebay.com> #20
I'm still facing this issue with AGP 8.2.2. Has the fix backported to 8.2.*?
an...@kakaopaycorp.com <an...@kakaopaycorp.com> #21
I am dying due to this.
Description
If a project has dynamic features enabled the install task generated for the application project is broken and will cause an stackoverflow in getApkFiles.
STEPS TO REPRODUCE:
1. Clone example project
2. Run ./gradlew app:installDebug
Output:
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ':app:installDebug'.
> A failure occurred while executing com.android.build.gradle.internal.tasks.InstallVariantViaBundleTask$InstallRunnable
> java.lang.StackOverflowError (no error message)
Full --stacktrace attached.
------------------
IMPORTANT: Please read
all required information.
------------------
Version of Gradle Plugin: 8.2.0
Version of Gradle: 8.5
Version of Java: 21
OS: Linux