Status Update
Comments
cl...@google.com <cl...@google.com>
ga...@gmail.com <ga...@gmail.com> #2
i donnot understand why is the data the same?
ga...@google.com <ga...@google.com>
bi...@google.com <bi...@google.com> #3
ga...@linecorp.com <ga...@linecorp.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.
ga...@linecorp.com <ga...@linecorp.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.
bi...@google.com <bi...@google.com>
ga...@linecorp.com <ga...@linecorp.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
ga...@linecorp.com <ga...@linecorp.com> #7
We have shared this with our product and engineering team and will update this issue with more information as it becomes available.
bi...@google.com <bi...@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.
cc...@google.com <cc...@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.
ga...@linecorp.com <ga...@linecorp.com> #10
bi...@google.com <bi...@google.com> #11
Thanks for trying it out and we are glad to see it works!
We don't plan to cherry-pick to 8.2 because we normally only do that for regression or critical bugs.
xa...@google.com <xa...@google.com> #12
Bingran, can you cherry-pick your fix to the hedgehog-dev branch? we're going to take this fix for Patch 1.
ey...@gmail.com <ey...@gmail.com> #13
So this was fixed three months ago, while Hedgehog was still in beta, and was a one liner, and couldn't be backported? What's the point of having beta and rc builds if reported bugs don't get fixed in them? Makes me question why I spend my time using the betas and rcs and report issues based on them.
xa...@google.com <xa...@google.com> #14
Yes, we dropped the ball, we should have cherry-picked this earlier.
bi...@google.com <bi...@google.com> #15
cherry-pick to hedgehog is landed I7f9faedeaeea0ae802d9a33930df116152ff2748
an...@google.com <an...@google.com> #16
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!
th...@gmail.com <th...@gmail.com> #17
Ignore this post. I initially only updated AS and missed to update AGP. Works for me with AGP 8.2.1 and openjdk 21.0.1.
so...@google.com <so...@google.com> #18
Comment added by automation: A postmortem has been automatically requested for this issue. Please author a postmortem on IRM. See go/android-postmortem-guidance for more context and details, including how to handle the case when this issue does not need a postmortem. If you have any questions not answered by go/android-postmortem-guidance, please email android-hygiene-tpm@, instead of reassigning the fixed bug. Thank you.
ma...@gmail.com <ma...@gmail.com> #19
Running Gradle task 'assembleDebug'...
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ':shared_preferences_android:compileDebugJavaWithJavac'.
> Could not resolve all files for configuration ':shared_preferences_android:androidJdkImage'.
> Failed to transform core-for-system-modules.jar to match attributes {artifactType=_internal_android_jdk_image, org.gradle.libraryelements=jar, org.gradle.usage=java-runtime}.
> Execution failed for JdkImageTransform: C:\Users\manor\AppData\Local\Android\sdk\platforms\android-34\core-for-system-modules.jar.
> Error while executing process C:\Program Files\Android\Android Studio1\jbr\bin\jlink.exe with arguments {--module-path C:\Users\manor\.gradle\caches\transforms-3\f41347c990b0e680f05f596924e70932\transformed\output\temp\jmod --add-modules java.base --output C:\Users\manor\.gradle\caches\transforms-3\f41347c990b0e680f05f596924e70932\transformed\output\jdkImage --disable-plugin system-modules}
* Try:
BUILD FAILED in 13s
┌─ Flutter Fix ────────────────────────────────────────────────────────────────────────────────────┐
│ [!] This is likely due to a known bug in Android Gradle Plugin (AGP) versions less than 8.2.1, │
│ when │
│ 1. setting a value for SourceCompatibility and │
│ 2. using Java 21 or above. │
│ To fix this error, please upgrade your AGP version to at least 8.2.1. The version of AGP that │
│ your project uses is likely defined in: │
│ D:\filmy_fun\android\settings.gradle, │
│ in the 'plugins' closure (by the number following "com.android.application"). │
│ Alternatively, if your project was created with an older version of the templates, it is likely │
│ in the buildscript.dependencies closure of the top-level build.gradle: │
│ D:\filmy_fun\android\build.gradle, │
│ as the number following "com.android.tools.build:gradle:". │
│ │
│ For more information, see: │
│
│
└──────────────────────────────────────────────────────────────────────────────────────────────────┘
Error: Gradle task assembleDebug failed with exit code 1
te...@gmail.com <te...@gmail.com> #20
any Solution of this??
fl...@gmail.com <fl...@gmail.com> #21
xa...@google.com <xa...@google.com> #22
If you are coming here via a link coming from Flutter, the solution is in the flutter output:
To fix this error, please upgrade your AGP version to at least 8.2.1
Description
DESCRIBE THE ISSUE IN DETAIL:
This is similar issue with b/294120922 , but it has different cause.
STEPS TO REPRODUCE:
I tried to perform
jlink
manually, I got following error message.IMPORTANT: Please readhttps://developer.android.com/studio/report-bugs.html carefully and supply
all required information.
Studio Build: 2022.3.1 OpenJDK 21 ea
Version of Gradle Plugin: 8.1.0
Version of Gradle: 8.2.1
Version of Java:
OS: Linux