Status Update
Comments
de...@squareup.com <de...@squareup.com> #2
i donnot understand why is the data the same?
dy...@google.com <dy...@google.com>
ju...@google.com <ju...@google.com>
ac...@google.com <ac...@google.com> #3
de...@squareup.com <de...@squareup.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...@squareup.com <de...@squareup.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.
de...@squareup.com <de...@squareup.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
bi...@google.com <bi...@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.
de...@squareup.com <de...@squareup.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.
bi...@google.com <bi...@google.com>
ga...@google.com <ga...@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.
bi...@google.com <bi...@google.com> #10
de...@squareup.com <de...@squareup.com> #11
I noticed that this has been pushed back until AGP 8.1. If we're able to do the work of implementing the proper fix for this issue, would you be open to accepting a patch to get this in for 8.0?
We're currently monkey-patching this locally using that patch to DexingTransform.kt
I submitted a while back which is proving to be an inconvenience for us to maintain as we upgrade AGP. So, if we're able to help expedite this fix by submitting a proper patch then that'd be great.
ga...@google.com <ga...@google.com> #12
We are actually discussing internally and with Gradle how to address this.
Current options are (not in any particular order):
- replace the filtering mechanism entirely: publish actual configuration from the base module that contains artifacts that need to be removed, and switch to something like
SubtractingArtifactCollection
that we already have - your proposal from #6: while it ensures different identity, I'm concerns about getting different output files on different machines, and ending up with multiple entries in the remote build cache. Consumers that care about file name or artifact identity will start getting cache misses.
- similar to 2), but using the input file content hash and appending it to the output file name. This ensures that identity and output file remain the same across different machines. Also, it is a bit tricky as we need to snapshot dirs.
- changing dex transforms from
java-classes-directory
->dex
withjar
->dex
in dynamic features. We already do this when desugaring classpath is requested, so with this we'll just lose incremental dexing for API 24+ in dynamic features for local subprojects.
My current recommendation is 4).
bi...@google.com <bi...@google.com> #13
Fixed with Ia029820623ada6a24b4d74024c962925b0387b53
hu...@google.com <hu...@google.com> #14
We decided to go with option 4: Disabling incremental dexing transforms for dynamic features (
This will likely slow down builds for dynamic features, so I've filed
Description
DESCRIBE THE ISSUE IN DETAIL:
With the following project structure:
app
modulelibrary
with some classes defined that also uses kapt/dagger2feature
which depends onlibrary
, and makes use of code fromlibrary
.Launching an activity from the
feature
module causes aNoClassDefFoundError
when trying to instantiate the class(es) defined in thelibrary
module.This only seems to happen when Dagger2 is applied to the
library
module and when code is generated via kapt. If all dagger-related code is removed from thelibrary
module then the class loading works fine. When dagger2 is applied it is actually also possible to instantiate the classes that are generated by dagger, despite the manually-defined classes being absent from the dex path.A project that reproduces this error is available here:https://github.com/dellisd/manifest-boom/tree/dagger-wtf (on that particular branch).
Another behaviour of this issue is that changing the app deploy method from "Default APK" to "APK from app bundle" fixes this issue in that project, however the same problem has been observed in other larger projects when using "APK from app bundle". It's been difficult to reproduce in a smaller project, but presumably it is related to the issue described here.
STEPS TO REPRODUCE:
ATTACH SCREENSHOTS/RECORDINGS OF THE ISSUE
ATTACH LOG FILES (Select Help > Show Log in Files, or Show Log in Finder on a Mac)
The output from these lines of code:https://github.com/dellisd/manifest-boom/blob/dagger-wtf/feature/src/main/java/com/example/manifestboom/feature/FirstFragment.kt#L26-L36
IMPORTANT: Please readhttps://developer.android.com/studio/report-bugs.html carefully and supply
all required information.
Studio Build: 2021.3.1 RC 1, #AI-213.7172.25.2113.8913347 Version of Gradle Plugin: 7.3.0-rc01 (also observed on 7.2.2) Version of Gradle: 7.4 Version of Java: 11 OS: macOS