Fixed

Bug

Status Update

No update yet.

Description

sa...@gmail.com

created issue #1

Aug 11, 2023 11:01AM

Attached file is a minimal reproducible example. It was created in the latest Android Studio (Hedgehog Canary 15). Template was a Kotlin project with no activity.

Three files were changed:

build.gradle.kts

isMinifyEnabled = true //necessary to cause the bug

implementation("com.github.SUPERCILEX.poi-android:poi:3.17")
implementation("com.github.SUPERCILEX.poi-android:proguard:3.17")

settings.gradle.kts

maven { url = uri("https://jitpack.io") }

proguard-rules.pro (I'm not sure if all rules are necessary to cause the bug)

-keeppackagenames org.apache.poi.ss.formula.function
-keeppackagenames org.apache.poi.ss.formula.functions

-keep public class com.fasterxml.aalto.** { *; }
-keep class org.apache.poi.** { *; }
-keep class org.apache.xmlbeans.** { *; }
-keep class org.codehaus.stax2.** { *; }
-keep class org.etsi.uri.x01903.**.impl.** { *; }
-keep class org.w3.x2000.impl.** { *; }
-keep class org.openxmlformats.schemas.**.impl.** { *; }
-keep class com.microsoft.schemas.**.impl.** { *; }

-keep class schemaorg_apache_xmlbeans.system.*.TypeSystemHolder { public final static *** typeSystem; }

Steps to reproduce

Open Android Studio
Menu -> Build -> Generate Signed Bundle / APK...
I chose APK, I don't know if it matters

Expected behaviour

Build finishes after about two minutes

Actual behaviour

Build stuck on :app:minifyReleaseWithR8 and never finishes, even after 14 hours

Build machine

Windows 11 22H2
AMD Ryzen 9 4900HS
I don't think it matters though, we saw the same issue on Azure Pipelines on Ubuntu and Windows images

Additional information

JDK 17, the one bundled with Android Studio
The issue started when we wanted to upgrade from Gradle build plugin 7.3.1 (when it still worked). Version 7.4.2 doesn't work anymore.

R8test.zip

27 MB

Download

Comments

ze...@google.com <ze...@google.com> Aug 11, 2023 11:50AM

Reassigned to ze...@google.com.

ze...@google.com <ze...@google.com> #2Aug 14, 2023 08:26AM

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?

ap...@google.com <ap...@google.com> #3Aug 14, 2023 12:16PM

the fractional part of the location data is exactly the same.

ze...@google.com <ze...@google.com> #4Aug 14, 2023 12:17PM

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.

ap...@google.com <ap...@google.com> #5Aug 15, 2023 01:18PM

Please provide the requested information to proceed further. Unfortunately the issue will be closed within 7 days if there is no further update.

ap...@google.com <ap...@google.com> #6Aug 15, 2023 01:18PM

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

ap...@google.com <ap...@google.com> #7Aug 16, 2023 05:05AM

We have shared this with our product and engineering team and will update this issue with more information as it becomes available.

ap...@google.com <ap...@google.com> #8Aug 16, 2023 05:05AM

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.

ap...@google.com <ap...@google.com> #9Aug 16, 2023 05:05AM

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.

ap...@google.com <ap...@google.com> #10Aug 16, 2023 05:05AM

Thank you very much! it is very useful to me . It solved my confusion.

ap...@google.com <ap...@google.com> #11Aug 16, 2023 05:05AM

Project: r8
Branch: 8.0

commit 5f3b6be71286d1d9e4c86685d4fe1e8b08764e2d
Author: Ian Zerny <zerny@google.com>
Date: Tue Aug 15 14:15:16 2023

Version 8.0.62

Bug:

b/295349278

Change-Id: Iba1c411ab51e9c31b3c86102d2c4a2c93baf8872

M src/main/java/com/android/tools/r8/Version.java

https://r8-review.googlesource.com/82466

ap...@google.com <ap...@google.com> #12Aug 16, 2023 05:05AM

Project: r8
Branch: 8.0

commit 650a62f183e4adeb4589a23646e26299bde21806
Author: Ian Zerny <zerny@google.com>
Date: Tue Aug 15 14:15:04 2023

Bail out of control-flow analysis on error states

This also changes the worklist usage to avoid pushing duplicates.

Bug:

b/295349278

Change-Id: I924e91f169a15eaf196647044a183917d2e57a83

M src/main/java/com/android/tools/r8/ir/analysis/framework/intraprocedural/AbstractTransferFunction.java
M src/main/java/com/android/tools/r8/ir/analysis/framework/intraprocedural/IntraProceduralDataflowAnalysisBase.java
M src/main/java/com/android/tools/r8/optimize/interfaces/analysis/CfFrameState.java
M src/main/java/com/android/tools/r8/optimize/interfaces/analysis/CfOpenClosedInterfacesAnalysis.java

https://r8-review.googlesource.com/82483

ze...@google.com <ze...@google.com> #13Aug 16, 2023 05:08AM

Thanks again for the report!

A fix for this has landed on our 4.0 branch targeting AGP 7.4. To enable it for your build you can amend your settings.gradle(.kt) with:

pluginManagement {
    buildscript {
        repositories {
            mavenCentral()
            maven {
                url = uri("https://storage.googleapis.com/r8-releases/raw")
            }
        }
        dependencies {
            classpath("com.android.tools:r8:4.0.67")
        }
    }
}

Fixes for later branches will land shortly. Let us know if this resolves your issue or if it fails to do so.

ap...@google.com <ap...@google.com> #14Aug 16, 2023 05:09AM

Project: r8
Branch: 8.2

commit 6f05498db081de4a171cb4a025aa8d829c5951cb
Author: Ian Zerny <zerny@google.com>
Date: Tue Aug 15 14:16:38 2023

Bail out of control-flow analysis on error states

This also changes the worklist usage to avoid pushing duplicates.

Bug:

b/295349278

https://r8-review.googlesource.com/82468

ap...@google.com <ap...@google.com> #15Aug 16, 2023 05:09AM

Project: r8
Branch: 8.1

commit 76937f44debe9453fe990ac539b284034c8124b9
Author: Ian Zerny <zerny@google.com>
Date: Tue Aug 15 14:15:53 2023

Bail out of control-flow analysis on error states

This also changes the worklist usage to avoid pushing duplicates.

Bug:

b/295349278

https://r8-review.googlesource.com/82467

ze...@google.com <ze...@google.com> Aug 17, 2023 08:53AM

Marked as fixed.

IssueTracker

Build gets stuck on :minifyReleaseWithR8 when using Apache POI library

Status Update

Description

Three files were changed:

Steps to reproduce

Additional information

Comments

ze...@google.com <ze...@google.com> Aug 11, 2023 11:50AM

ze...@google.com <ze...@google.com> #2Aug 14, 2023 08:26AM

ap...@google.com <ap...@google.com> #3Aug 14, 2023 12:16PM

ze...@google.com <ze...@google.com> #4Aug 14, 2023 12:17PM

ap...@google.com <ap...@google.com> #5Aug 15, 2023 01:18PM

ap...@google.com <ap...@google.com> #6Aug 15, 2023 01:18PM

ap...@google.com <ap...@google.com> #7Aug 16, 2023 05:05AM

ap...@google.com <ap...@google.com> #8Aug 16, 2023 05:05AM

ap...@google.com <ap...@google.com> #9Aug 16, 2023 05:05AM

ap...@google.com <ap...@google.com> #10Aug 16, 2023 05:05AM

ap...@google.com <ap...@google.com> #11Aug 16, 2023 05:05AM

ap...@google.com <ap...@google.com> #12Aug 16, 2023 05:05AM

ze...@google.com <ze...@google.com> #13Aug 16, 2023 05:08AM

ap...@google.com <ap...@google.com> #14Aug 16, 2023 05:09AM

ap...@google.com <ap...@google.com> #15Aug 16, 2023 05:09AM

ze...@google.com <ze...@google.com> Aug 17, 2023 08:53AM

Issue 295349278

Description

Three files were changed:

Steps to reproduce

Additional information

Issue summary

Comments

ze...@google.com <ze...@google.com> Aug 11, 2023 11:50AM

ze...@google.com <ze...@google.com> #2Aug 14, 2023 08:26AM

ap...@google.com <ap...@google.com> #3Aug 14, 2023 12:16PM

ze...@google.com <ze...@google.com> #4Aug 14, 2023 12:17PM

ap...@google.com <ap...@google.com> #5Aug 15, 2023 01:18PM

ap...@google.com <ap...@google.com> #6Aug 15, 2023 01:18PM

ap...@google.com <ap...@google.com> #7Aug 16, 2023 05:05AM

ap...@google.com <ap...@google.com> #8Aug 16, 2023 05:05AM

ap...@google.com <ap...@google.com> #9Aug 16, 2023 05:05AM

ap...@google.com <ap...@google.com> #10Aug 16, 2023 05:05AM

ap...@google.com <ap...@google.com> #11Aug 16, 2023 05:05AM

ap...@google.com <ap...@google.com> #12Aug 16, 2023 05:05AM

ze...@google.com <ze...@google.com> #13Aug 16, 2023 05:08AM

ap...@google.com <ap...@google.com> #14Aug 16, 2023 05:09AM

ap...@google.com <ap...@google.com> #15Aug 16, 2023 05:09AM

ze...@google.com <ze...@google.com> Aug 17, 2023 08:53AM

Add comment

Issue metadata