Status Update
No update yet.
Comments
uc...@google.com
dn...@google.com
dn...@google.com
lb...@gmail.com
i donnot understand why is the data the same?
xo...@google.com
tn...@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.
lb...@gmail.com
Please provide the requested information to proceed further. Unfortunately the issue will be closed within 7 days if there is no further update.
dn...@google.com
bl...@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
xo...@google.com
We have shared this with our product and engineering team and will update this issue with more information as it becomes available.
lb...@gmail.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.
bl...@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.
xo...@google.com
lb...@gmail.com
Why does it occur? Why isn't there any button there to tell it to update? Why doesn't it tell what triggered it to be of a different version?
Look at the attached screenshot to understand what I mean.
xo...@google.com
Without seeing the whole project definition, it's difficult to diagnose what's going on. Please open a new ticket for investigation on any issue that isn't directly related to missing suggestions to upgrade BoM dependencies.
lb...@gmail.com
I have these:
implementation platform('com.google.firebase:firebase-bom:32.6.0')
implementation "com.google.firebase:firebase-analytics"
implementation "com.google.firebase:firebase-crashlytics"
I don't even know what it is that I'm seeing, so I ask you.
As you can see on the screenshot, it's not always for Firebase either
Should it have a new ticket?
xo...@google.com
Yes, please file a new ticket.
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 Iguana | 2023.2.1 Canary 17
- Android Gradle Plugin 8.3.0-alpha17
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!
lb...@gmail.com
I still see the message of "Gradle promoted library version to ...".
Android Studio Iguana | 2023.2.1 Canary 17
Build #AI-232.10227.8.2321.11191411, built on December 7, 2023
Runtime version: 17.0.9+0--11185874 amd64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.
Windows 11.0
GC: G1 Young Generation, G1 Old Generation
Memory: 3072M
Cores: 12
Registry:
debugger.watches.in.variables=false
Non-Bundled Plugins:
Show As ... (1.1.1)
cn.jxzhang.plugin.json-formatter (1.4)
com.intellij.marketplace (232.10227.13)
String Manipulation (9.12.0)
GenerateSerialVersionUID (3.0.3)
idea.plugin.protoeditor (232.9559.10)
com.steve.plugins.autoscroll (1.1)
com.dethlex.numberconverter (1.5.0)
izhangzhihao.rainbow.brackets (2023.3.7)
com.ppismerov.ksvu (0.0.1)
net.aquadc.mike.plugin (0.30)
com.developerphil.adbidea (1.6.13)
GenerateSerializationHelpers (1.0.6)
Description
Version of Gradle Plugin:
Version of Gradle:
Version of Java:
OS:
Android Studio 4.2.1
Build #AI-202.7660.26.42.7351085, built on May 10, 2021
Runtime version: 11.0.8+10-b944.6842174 amd64
VM: OpenJDK 64-Bit Server VM by N/A
Windows 10 10.0
GC: G1 Young Generation, G1 Old Generation
Memory: 4000M
Cores: 12
Registry: external.system.auto.import.disabled=true, ide.settings.move.mouse.on.default.button=true, debugger.watches.in.variables=false
Non-Bundled Plugins: String Manipulation, org.jetbrains.kotlin, com.google.mad-scorecard, org.intellij.plugins.markdown, GenerateSerialVersionUID
Steps to Reproduce:
1. Say you use Firebase Crashlytics and Analytics:
implementation platform('com.google.firebase:firebase-bom:28.0.1')
implementation 'com.google.firebase:firebase-analytics-ktx'
implementation 'com.google.firebase:firebase-crashlytics-ktx'
2. Look at it on gradle file and on "Suggestions", as there is a new version:
The bug is that nothing is showing that there is a new version of it (which is 28.1.0).