Status Update
No update yet.
Comments
lb...@gmail.com
i donnot understand why is the data the same?
cm...@google.com
je...@google.com
cm...@google.com
lb...@gmail.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.
cm...@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
lb...@gmail.com
We have shared this with our product and engineering team and will update this issue with more information as it becomes available.
cm...@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.
lb...@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.
cm...@google.com
lb...@gmail.com
I tried CTRL+ALT+S (File->settings) and I don't see those there.
Perhaps you are talking about some configuration file? If so, please offer it on a nice UI too.
vm...@google.com
To open the Gradle Settings you have different ways:
- Settings > Build Execution Deployment > Build Tools > Gradle
- File > Project Structure > SDK Location > Gradle Settings
- Searching for action
Change Gradle JDK Location
lb...@gmail.com
Attached video about this.
And as you can see, it's sadly per project. I can't find a way to set it as default. It's actually even showing there is a default, but it doesn't use it by default when I create a new project.
Each time I create a new project, it chooses something wrong, and I have to choose the embedded one (which is marked as default) again, and again.
It takes now about 3 minutes or so to create a Hello-world project on Canary.
vm...@google.com
Let's recap a bit the different points mentioned:
Using the searching bar on Settings isn't displaying Gradle JDK:
- That's correct, however, seems to be quite buggy and sometimes searching by
Gradleworks. In any case, let's use thisnew ticket
Why we are not using
Android Studio default jdk:
- This
jdk.tableentry is a hardcoded naming causing issues especially when used in different machines that may have their jdk.table pointing to a completely different JDK version. For this reason, we migrate away from them using the standard vendor + version i.e jbr-17. For this reason, we just have them for compatibility reasons with older project/AS versions
Each time I create a new project, it chooses something wrong.
- There was an issue regarding this that was addressed as part of this internal bug
273803862, and is caused by the fact of using the firstjdk.tableentry for the new created projects. This was addressed by using theEmbedded JDKand those changes are going to land inAndroid Studio G Beta 1. In addition, in the near future we are going to allow users to modify this selection from "Default project structure" option.
I hope this helped to clarify, in any case, will be great to keep things separate to avoid mixing different bugs for the same report.
lb...@gmail.com
Why can't there be a button "Set this as default" which will set it for every new project created, and also change to it in case there is an issue related to gradle when you open an existing project?
Such a thing should exist in other places, too.
For me, for example, I always choose "show Logcat automatically" and "Clear log before launch" in the run-configuration. I have to set it for every project I create/open...
vm...@google.com
As a workaround for your problem with new created projects, you can manually delete your Android studio jdk.table.xml from JavaSDK type. Here is a sample about those paths:
macOS: ~/Library/Application Support/Google/AndroidStudio-VERSION/options/jdk.table.xml
linux: ~/.config/Google/AndroidStudio-VERSION/options/jdk.table.xml
windows: %APPDATA%\Google\AndroidStudio-VERSION\options\jdk.table.xml
As mentioned a fix will land in Android Studio G Beta 1 addressing this issue for new created projects.
Regarding your second point, the Default project structure is already present under File > New Project Setup allowing users to define their default SDK and NDK. For consistency reasons were added to that specific UI, considering that the JDK selected in the Gradle Settings only applies to the selected Gradle root but users may have projects with multiple Gradle roots.
In any case, please feel free to create any feature request ticket that will be reviewed and discussed properly keeping this ticket for stuff only related to its title. Thank you
lb...@gmail.com
vm...@google.com
On the APPDATA is for example C:\Users\YourUserName\AppData\Roaming:
%APPDATA%\Google\AndroidStudio-VERSION\options\jdk.table.xml
lb...@gmail.com
Choosing on AndroidStudioPreview2022.3 which seems the latest for canary (how is it 2022?), I deleted the file jdk.table.xml there and then started the IDE.
Then it asked me which JDK to use for gradle.
Then as it opened an existing project, it marked plenty of things in red, related to view-binding, as if they don't exist. Restarting the IDE fixed it.
For a new project, the issue of needing to change gradle JDK version is gone.
In any case, the original issue that I talked about needs fixing.
Please also improve the settings and backward compatibility.
vm...@google.com
This exception is linked with JDK < 17, on studio version using JDK 17. I was able to reproduce it on a sample project with the following configuration:
JDK 11
Gradle 7.2.0
AGP 4.2.2
The project builds properly from the command line and as a workaround, you need to update your project to the most recent AGP/Gradle version that require JDK 17. In any case, a fix will land soon on AS H Canary 2 and will also be cherrypicked on AS G Beta 3. Please feel free to retest the mentioned versions. Thank you
lb...@gmail.com
I see this a lot, that an "old" project (can even be just 1 year old) can't be opened anymore, and requires various manual steps while the IDE doesn't help much at all, showing "random" errors without any useful clue about what's wrong.
Maybe offer for all build-errors (or at least those that IDE fails to offer a good quick-fix, or when we tried its quick-fix, and it still failed) an automatic check that gets added, to upgrade what you've written (gradle and AGP).
ja...@gmail.com
Caused by: java.lang.UnsupportedOperationException: PermittedSubclasses requires ASM9
at org.objectweb.asm.ClassVisitor.visitPermittedSubclass(ClassVisitor.java:281)
at org.objectweb.asm.ClassReader.accept(ClassReader.java:707)
at org.objectweb.asm.ClassReader.accept(ClassReader.java:425)
at com.android.build.gradle.tasks.DependenciesAnalyzer.visitClass(DependenciesAnalyzer.kt:70)
This issue is because:
class DependenciesAnalyzer {
private val asmVersion = Opcodes.ASM7
}
Description
Example attached here.
Please have a better backward compatibility on the IDE, offer proper information that we can do something about it, and offer a quick-fix for each case that is known.