Status Update
No update yet.
Comments
aa...@google.com
je...@google.com
ja...@gmail.com
i donnot understand why is the data the same?
ja...@gmail.com
ja...@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.
ja...@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.
ja...@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
bi...@google.com
We have shared this with our product and engineering team and will update this issue with more information as it becomes available.
ja...@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.
sg...@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.
ja...@gmail.com
bi...@google.com
In AGP 8.2, there will be an optional boolean flag called android.enableApiModelingAndGlobalSynthetics which you can use to disable api modeling. It should be available from 8.2 alpha03.
In AGP 8.1, the cherry-pick is not landed yet so currently there isn't a way to disable api modeling from AGP.
ja...@gmail.com
Hm, okay. Just trying to find a way to work around this without waiting for the next 8.1.0 to be released in two weeks. I could repack the apk after round-tripping it through baksmali/smali as part of the build, but that seems excessive.
ze...@google.com
As a temporary workaround, you should be able to set the system property -Dcom.android.tools.r8.disableApiModeling=1 as a command line option to the gradle build command. That should disable the modeling in the compiler.
ja...@gmail.com
Thanks. I thought I'd tried that via the gradle file, but it didn't work. Turns out it was just a build cache issue.
So, adding System.setProperty("com.android.tools.r8.disableApiModeling", "1") to my build.gradle.kts seems to do the trick too.
sg...@google.com
After trying to reproduce the issue again I found that the analysis in
.class public LA;
.super Landroid/service/quicksettings/TileService;
.method public constructor <init>()V
.locals 0
invoke-direct {p0}, Landroid/service/quicksettings/TileService;-><init>()V
return-void
.end method
.method public x()V
.locals 3
const/4 v0, 0x0
invoke-super {p0, v0}, Landroid/service/quicksettings/TileService;->onBind(Landroid/content/Intent;)Landroid/os/IBinder;
return-void
.end method
.class public synthetic Landroid/service/quicksettings/TileService;
.super Landroid/app/Service;
.method static synthetic constructor <clinit>()V
.locals 1
new-instance v0, Ljava/lang/NoClassDefFoundError;
invoke-direct {v0}, Ljava/lang/NoClassDefFoundError;-><init>()V
throw v0
.end method
Addng a constructor to android/service/quicksettings/TileService did not make a difference, but adding an onBind method did fix/workaround the issue.
.method public onBind(Landroid/content/Intent;)Landroid/os/IBinder;
.locals 2
const/4 p1, 0x0
return-object p1
.end method
I have now been testing on a Nexus 4 with Android 5.0.2, and there I cannot reproduce the issue (yet). So for now this is only known to happen on x86 emulators on 5.0.
ap...@google.com
Branch: main
commit 77e3c9ee8166f30ebd471784d37d1f47e8c529ee
Author: Morten Krogh-Jespersen <mkroghj@google.com>
Date: Mon May 15 12:37:19 2023
[ApiModel] Disable stubbing of super classes on L and below
Bug:
Change-Id: I1afd04dcb2134815162f073e186d25d2c61f6fca
M src/main/java/com/android/tools/r8/androidapi/ApiReferenceStubber.java
M src/test/java/com/android/tools/r8/apimodel/ApiModelD8GradleSetupTest.java
M src/test/java/com/android/tools/r8/apimodel/ApiModelMockInheritedClassTest.java
M src/test/java/com/android/tools/r8/apimodel/ApiModelMockRetraceTest.java
M src/test/java/com/android/tools/r8/apimodel/ApiModelMockSuperChainClassTest.java
M src/test/java/com/android/tools/r8/apimodel/ApiModelingTestHelper.java
ap...@google.com
Branch: 8.0
commit 0b06f25340736645e31672e5e98deabb366b9921
Author: Morten Krogh-Jespersen <mkroghj@google.com>
Date: Tue May 16 09:27:51 2023
Version 8.0.47
Bug:
Bug:
Bug:
Bug:
Change-Id: I8ea8c490d6d0e733e300728c77d8feddde9aa312
M src/main/java/com/android/tools/r8/Version.java
ap...@google.com
Branch: 8.0
commit a4f37fe81ba59e950f31ceef599b146bb29aa772
Author: Morten Krogh-Jespersen <mkroghj@google.com>
Date: Tue May 16 09:27:33 2023
[ApiModel] Disable stubbing of super classes on L and below
Bug:
Change-Id: I1afd04dcb2134815162f073e186d25d2c61f6fca
M src/main/java/com/android/tools/r8/androidapi/ApiReferenceStubber.java
M src/test/java/com/android/tools/r8/apimodel/ApiModelMockInheritedClassTest.java
M src/test/java/com/android/tools/r8/apimodel/ApiModelMockSuperChainClassTest.java
M src/test/java/com/android/tools/r8/apimodel/ApiModelingTestHelper.java
ap...@google.com
Branch: 8.1
commit d0af1518cea3186af14296f7eaccae005fa654d0
Author: Morten Krogh-Jespersen <mkroghj@google.com>
Date: Mon May 15 18:02:40 2023
Version 8.1.47
Bug:
Change-Id: If9242211ae882869e74c278816f25dc3d96d3b4f
M src/main/java/com/android/tools/r8/Version.java
ap...@google.com
Branch: 8.1
commit 4d3d76666187e933b3ef943ff7301bb90a4f37fb
Author: Morten Krogh-Jespersen <mkroghj@google.com>
Date: Mon May 15 18:01:59 2023
[ApiModel] Disable stubbing of super classes on L and below
Bug:
Change-Id: I1afd04dcb2134815162f073e186d25d2c61f6fca
M src/main/java/com/android/tools/r8/androidapi/ApiReferenceStubber.java
M src/test/java/com/android/tools/r8/apimodel/ApiModelD8GradleSetupTest.java
M src/test/java/com/android/tools/r8/apimodel/ApiModelMockInheritedClassTest.java
M src/test/java/com/android/tools/r8/apimodel/ApiModelMockRetraceTest.java
M src/test/java/com/android/tools/r8/apimodel/ApiModelMockSuperChainClassTest.java
M src/test/java/com/android/tools/r8/apimodel/ApiModelingTestHelper.java
ap...@google.com
Branch: 8.0
commit a4f37fe81ba59e950f31ceef599b146bb29aa772
Author: Morten Krogh-Jespersen <mkroghj@google.com>
Date: Tue May 16 09:27:33 2023
[ApiModel] Disable stubbing of super classes on L and below
Bug:
Change-Id: I1afd04dcb2134815162f073e186d25d2c61f6fca
M src/main/java/com/android/tools/r8/androidapi/ApiReferenceStubber.java
M src/test/java/com/android/tools/r8/apimodel/ApiModelMockInheritedClassTest.java
M src/test/java/com/android/tools/r8/apimodel/ApiModelMockSuperChainClassTest.java
M src/test/java/com/android/tools/r8/apimodel/ApiModelingTestHelper.java
Description
When I compile my app with agp 8.0.0, everything is fine. When I compile it with 8.1.0, and then install it onto the API 21 emulator, the installation fails. Logcat reveals this catastrophe: