Fixed
Status Update
No update yet.
Comments
ar...@google.com
je...@google.com
am...@google.com
am...@google.com
ch...@kogan.com.au
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?
i donnot understand why is the data the same?
mi...@mikehardy.net
the fractional part of the location data is exactly the same.
am...@google.com
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.
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.
wb...@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.
mi...@mikehardy.net
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
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
am...@google.com
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
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
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.
wb...@gmail.com
Thank you very much! it is very useful to me . It solved my confusion.
mi...@mikehardy.net
This bug is not fixed. Same repro (build repo https://github.com/ankidroid/Anki-Android with new android gradle plugin by editing top level `build.gradle` by altering line 19 to have new version using command `./gradlew jacocoUnitTestReport`
Same error
> Task :AnkiDroid:generatePlayDebugUnitTestConfig FAILED
None of these versions work:
- 8.1.2
- 8.2.0-beta06
- 8.3.0-alpha06
Same error
> Task :AnkiDroid:generatePlayDebugUnitTestConfig FAILED
None of these versions work:
- 8.1.2
- 8.2.0-beta06
- 8.3.0-alpha06
am...@google.com
mi...@mikehardy.net
You indicate: "If you notice further issues or have questions, please file a new bug report."
Google issues says "You do not have permission to create issues in this component." :-)
Regardless, I have logged this issue per direction to log a new issue:https://issuetracker.google.com/issues/302961829
Google issues says "You do not have permission to create issues in this component." :-)
Regardless, I have logged this issue per direction to log a new issue:
am...@google.com
The change that addresses this issue is in code review. Expect an update soon.
xa...@google.com
Fix was merged in the Hedgehog branch so the next beta build should have the fix.
We are considering a patch for G/8.1
de...@bayer.com
Any updates on deadlines of when that will be patched to G/8.1 into Giraffe Patch 3? We're currently unable to run our Unit tests due to this issue. We have the following in our gradle file.
testOptions {
animationsDisabled = true
unitTests {
includeAndroidResources = true
}
}
splits {
abi {
enable true
reset()
include 'x86_64', 'arm64-v8a', 'armeabi-v7a'
universalApk true
}
}
I get the same errors as described by #10
expected one element but was: <BuiltArtifactImpl(outputFile=<project>/build/intermediates/packaged_manifests/debug/armeabi-v7a/AndroidManifest.xml, versionCode=1, versionName=1.0, variantOutputConfiguration=VariantOutputConfigurationImpl(isUniversal=false, filters=[FilterConfiguration(filterType=ABI, identifier=armeabi-v7a)]), attributes={}), BuiltArtifactImpl(outputFile=<project>/build/intermediates/packaged_manifests/debug/x86_64/AndroidManifest.xml, versionCode=1, versionName=1.0, variantOutputConfiguration=VariantOutputConfigurationImpl(isUniversal=false, filters=[FilterConfiguration(filterType=ABI, identifier=x86_64)]), attributes={}), BuiltArtifactImpl(outputFile=<project>/build/intermediates/packaged_manifests/debug/x86/AndroidManifest.xml, versionCode=1, versionName=1.0, variantOutputConfiguration=VariantOutputConfi gurationImpl(isUniversal=false, filters=[FilterConfiguration(filterType=ABI, identifier=x86)]), attributes={})>
If I remove the includeAndroidResources = true I can compile the Unit Tests however some of them fail as they cannot access android resources any longer and they rely on it.
testOptions {
animationsDisabled = true
unitTests {
includeAndroidResources = true
}
}
splits {
abi {
enable true
reset()
include 'x86_64', 'arm64-v8a', 'armeabi-v7a'
universalApk true
}
}
I get the same errors as described by #10
expected one element but was: <BuiltArtifactImpl(outputFile=<project>/build/intermediates/packaged_manifests/debug/armeabi-v7a/AndroidManifest.xml, versionCode=1, versionName=1.0, variantOutputConfiguration=VariantOutputConfigurationImpl(isUniversal=false, filters=[FilterConfiguration(filterType=ABI, identifier=armeabi-v7a)]), attributes={}), BuiltArtifactImpl(outputFile=<project>/build/intermediates/packaged_manifests/debug/x86_64/AndroidManifest.xml, versionCode=1, versionName=1.0, variantOutputConfiguration=VariantOutputConfigurationImpl(isUniversal=false, filters=[FilterConfiguration(filterType=ABI, identifier=x86_64)]), attributes={}), BuiltArtifactImpl(outputFile=<project>/build/intermediates/packaged_manifests/debug/x86/AndroidManifest.xml, versionCode=1, versionName=1.0, variantOutputConfiguration=VariantOutputConfi gurationImpl(isUniversal=false, filters=[FilterConfiguration(filterType=ABI, identifier=x86)]), attributes={})>
If I remove the includeAndroidResources = true I can compile the Unit Tests however some of them fail as they cannot access android resources any longer and they rely on it.
de...@bayer.com
We got a new RC release for Hedgehog https://androidstudio.googleblog.com/2023/10/android-studio-hedgehog-202311-rc-1-now.html and this issue isn't listed in there as fixed, is there a plan of when/where this will be patched?
am...@google.com
The fix for this bug is already in Iguana Canary 7 and is going to be included in Hedgehog RC2 and Giraffe P3.
de...@bayer.com
Just tested on Android Studio Iguana | 2023.2.1 Canary 11
Build #AI-232.10072.27.2321.11006994, built on October 26, 2023
Runtime version: 17.0.8+0-17.0.8b1000.22-10799086 aarch64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.
macOS 13.6.1
GC: G1 Young Generation, G1 Old Generation
Memory: 2048M
Cores: 10
Metal Rendering is ON
Registry:
external.system.auto.import.disabled=true
debugger.new.tool.window.layout=true
ide.text.editor.with.preview.show.floating.toolbar=false
ide.experimental.ui=true
Non-Bundled Plugins:
idea.plugin.protoeditor (232.9559.10)
And the issue persists (the exact same issue)
Build #AI-232.10072.27.2321.11006994, built on October 26, 2023
Runtime version: 17.0.8+0-17.0.8b1000.22-10799086 aarch64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.
macOS 13.6.1
GC: G1 Young Generation, G1 Old Generation
Memory: 2048M
Cores: 10
Metal Rendering is ON
Registry:
external.system.auto.import.disabled=true
debugger.new.tool.window.layout=true
ide.text.editor.with.preview.show.floating.toolbar=false
ide.experimental.ui=true
Non-Bundled Plugins:
idea.plugin.protoeditor (232.9559.10)
And the issue persists (the exact same issue)
de...@bayer.com
Also tested on Android Studio Hedgehog | 2023.1.1 RC 2
Build #AI-231.9392.1.2311.10980684, built on October 20, 2023
Runtime version: 17.0.7+0-17.0.7b1000.6-10550314 aarch64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.
macOS 13.6.1
GC: G1 Young Generation, G1 Old Generation
Memory: 2048M
Cores: 10
Metal Rendering is ON
Registry:
external.system.auto.import.disabled=true
debugger.new.tool.window.layout=true
ide.text.editor.with.preview.show.floating.toolbar=false
ide.experimental.ui=true
Non-Bundled Plugins:
idea.plugin.protoeditor (231.9225.5)
No success (Same issue is still present)
Build #AI-231.9392.1.2311.10980684, built on October 20, 2023
Runtime version: 17.0.7+0-17.0.7b1000.6-10550314 aarch64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.
macOS 13.6.1
GC: G1 Young Generation, G1 Old Generation
Memory: 2048M
Cores: 10
Metal Rendering is ON
Registry:
external.system.auto.import.disabled=true
debugger.new.tool.window.layout=true
ide.text.editor.with.preview.show.floating.toolbar=false
ide.experimental.ui=true
Non-Bundled Plugins:
idea.plugin.protoeditor (231.9225.5)
No success (Same issue is still present)
am...@google.com
Can you please check the AGP version you are using?
de...@bayer.com
Updating gradle to 8.2.0-rc02 on Android Studio Hedgehog | 2023.1.1 RC 2 seems to solve this issue. Thank you all!
an...@google.com
Further fixes for this issue are now available in:
- Android Studio Giraffe | 2022.3.1 Patch 3
- Android Gradle Plugin 8.1.3
We encourage you to try the latest update.
If you notice further issues or have questions, please file a new bug report.
be...@gmail.com
My area support on
na...@gmail.com
Good 👍
19...@gmail.com
Comment has been deleted.
sh...@gmail.com Restricted+
Restricted+
Comment has been deleted.
Description
./gradlewtest fails with "Unable to find manifest output" if bothsplits.abi.isEnableandtestOptions.unitTests.isIncludeAndroidResourcesare true.Disabling either of the options allows the command to finish successfully.
This is not reproducible on AGP 8.0.2.
A reproducer can be found at