NoClassDefFoundError for java.lang.reflect.Executable [289361079]

Fixed

Bug

Status Update

No update yet.

Description

ku...@gmail.com

created issue #1

Jun 29, 2023 03:16PM

# compiler: R8
# compiler_version: 8.0.53
# fullmode: true

App crases on Android 7

FATAL EXCEPTION: main
Process: com.example.myapplication, PID: 24480
java.lang.NoClassDefFoundError: Failed resolution of: Ljava/lang/reflect/Executable;
	at kotlin.ResultKt.get(SourceFile:22)
	at kotlin.Result$Companion.toString(SourceFile:20)
	at com.example.myapplication.MainActivity.onCreate(SourceFile:12)
	at android.app.Activity.performCreate(Activity.java:6662)
	at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1118)
	at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2599)
	at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2707)
	at android.app.ActivityThread.-wrap12(ActivityThread.java)
	at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1460)
	at android.os.Handler.dispatchMessage(Handler.java:102)
	at android.os.Looper.loop(Looper.java:154)
	at android.app.ActivityThread.main(ActivityThread.java:6077)
	at java.lang.reflect.Method.invoke(Native Method)
	at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:866)
	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:756)
Caused by: java.lang.ClassNotFoundException: Didn't find class "java.lang.reflect.Executable" on path: DexPathList[[zip file "/data/app/com.example.myapplication-1/base.apk"],nativeLibraryDirectories=[/data/app/com.example.myapplication-1/lib/x86_64, /system/lib64, /vendor/lib64]]
	at dalvik.system.BaseDexClassLoader.findClass(BaseDexClassLoader.java:56)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:380)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:312)
	at kotlin.ResultKt.get(SourceFile:22) 
	at kotlin.Result$Companion.toString(SourceFile:20) 
	at com.example.myapplication.MainActivity.onCreate(SourceFile:12) 
	at android.app.Activity.performCreate(Activity.java:6662) 
	at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1118) 
	at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2599) 
	at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2707) 
	at android.app.ActivityThread.-wrap12(ActivityThread.java) 
	at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1460) 
	at android.os.Handler.dispatchMessage(Handler.java:102) 
	at android.os.Looper.loop(Looper.java:154) 
	at android.app.ActivityThread.main(ActivityThread.java:6077) 
	at java.lang.reflect.Method.invoke(Native Method) 
	at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:866) 
	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:756)

FailedResolution.7z

93 KB

Download

Comments

ze...@google.com <ze...@google.com> #2Jun 29, 2023 03:29PM

Reassigned to ze...@google.com.

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?

ku...@gmail.com <ku...@gmail.com> #3Jun 29, 2023 04:46PM

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

ze...@google.com <ze...@google.com> #4Jun 30, 2023 08:56AM

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.

ku...@gmail.com <ku...@gmail.com> #5Jun 30, 2023 09:23AM

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

ze...@google.com <ze...@google.com> #6Jun 30, 2023 10:34AM

Reassigned to mk...@google.com.

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

mk...@google.com <mk...@google.com> #7Jul 4, 2023 10:35AM

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

ku...@gmail.com <ku...@gmail.com> #8Jul 6, 2023 01:28PM

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.

mk...@google.com <mk...@google.com> #9Jul 6, 2023 01:29PM

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> #10Jul 7, 2023 10:01AM

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

ap...@google.com <ap...@google.com> #11Jul 7, 2023 10:01AM

Project: r8
Branch: main

commit ad3e5defb88d164a5a4254f6e61a908da47e5011
Author: Morten Krogh-Jespersen <mkroghj@google.com>
Date: Fri Jul 07 11:19:06 2023

Add test for rewriting of merged constructor to newer api type

Bug:

b/289361079

Change-Id: I28d1bbfaba5249aa789f8ed47e68bbf915c04926

A src/test/java/com/android/tools/r8/classmerging/horizontal/ClInitMergeSuperTypeApiLevelTest.java
M src/test/java/com/android/tools/r8/utils/codeinspector/TypeSubject.java

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

ap...@google.com <ap...@google.com> #12Jul 11, 2023 01:10PM

Project: r8
Branch: 8.1

commit 37f711090c766587b47207027c136a4f7ff4cbf4
Author: Morten Krogh-Jespersen <mkroghj@google.com>
Date: Tue Jul 11 10:21:27 2023

Version 8.1.59

Bug:

b/289361079

Change-Id: I6b25e0a05e1ca410e249276a5bc718d9449487d3

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

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

ap...@google.com <ap...@google.com> #13Jul 11, 2023 01:10PM

Project: r8
Branch: 8.1

commit c0e7df085b8a905b55f8baf738d8bc791fa4b2c0
Author: Morten Krogh-Jespersen <mkroghj@google.com>
Date: Tue Jul 11 10:21:16 2023

Ensure that merged parameter is api safe

Bug:

b/289361079

Change-Id: Ifa30fed27c283906b9ce89835ba8c268c9430190

M src/main/java/com/android/tools/r8/graph/DexTypeUtils.java
M src/test/java/com/android/tools/r8/classmerging/horizontal/ClInitMergeSuperTypeApiLevelTest.java

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

ap...@google.com <ap...@google.com> #14Jul 11, 2023 01:10PM

Project: r8
Branch: 8.1

commit d2a198434799da1a13f7819cee31f2addcd87c35
Author: Morten Krogh-Jespersen <mkroghj@google.com>
Date: Tue Jul 11 10:21:04 2023

Add test for rewriting of merged constructor to newer api type

Bug:

b/289361079

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

ap...@google.com <ap...@google.com> #15Jul 12, 2023 10:35AM

Project: r8
Branch: 8.0

commit 8ddade1a3107b288105d14860b58a15a14c9b484
Author: Morten Krogh-Jespersen <mkroghj@google.com>
Date: Wed Jul 12 09:49:48 2023

Version 8.0.57

Bug:

b/289361079

Change-Id: Ia027d76f698ce4a4d2a2ef22218e9462fcef7e8c

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

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

ap...@google.com <ap...@google.com> #16Jul 12, 2023 10:35AM

Project: r8
Branch: 8.0

commit e5088be717104530fa360b67acde8ab0619bca6a
Author: Morten Krogh-Jespersen <mkroghj@google.com>
Date: Wed Jul 12 09:49:38 2023

Ensure that merged parameter is api safe

Bug:

b/289361079

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

ap...@google.com <ap...@google.com> #17Jul 12, 2023 10:35AM

Project: r8
Branch: 8.0

commit da09d4f505a8c26b8e2f752e75c59c7edabfcf14
Author: Morten Krogh-Jespersen <mkroghj@google.com>
Date: Wed Jul 12 09:49:25 2023

Add test for rewriting of merged constructor to newer api type

Bug:

b/289361079

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

mk...@google.com <mk...@google.com> #18Jul 12, 2023 01:21PM

I just verified that running with version 8.0.57 in the reproduction solves the issue. I cannot speak to when this will be merged into AGP/Studio, but for anyone else seeing this problem, you can define the dependency by modifying build.gradle :

buildscript {
    dependencies {
        classpath 'com.android.tools:r8:8.0.57'  // Must be before the Gradle Plugin for Android.
    }
}

and settings.gradle:

pluginManagement {
    repositories {
        google()
        mavenCentral()
        gradlePluginPortal()
        maven {
            url 'https://storage.googleapis.com/r8-releases/raw'
        }
    }
}
dependencyResolutionManagement {
    repositoriesMode.set(RepositoriesMode.FAIL_ON_PROJECT_REPOS)
    repositories {
        google()
        mavenCentral()
        maven {
            url 'https://storage.googleapis.com/r8-releases/raw'
        }
    }
}

mk...@google.com <mk...@google.com> Jul 14, 2023 07:33AM

Marked as fixed.

vl...@gmail.com <vl...@gmail.com> #19Jan 23, 2024 10:45AM

Was this fixed and what version?

ze...@google.com <ze...@google.com> #20Jan 23, 2024 12:07PM

This fix did not make any releases of AGP 8.0 or for the release of AGP 8.1.0. If you are using either of those you will need to manually link to a fixed R8 version as detailed in comment #18.

This fix is included in AGP 8.1.1 (which shipped with R8 version 8.1.65) and onward.

Issue 289361079

Description

Issue summary

Comments

ze...@google.com <ze...@google.com> #2Jun 29, 2023 03:29PM

ku...@gmail.com <ku...@gmail.com> #3Jun 29, 2023 04:46PM

ze...@google.com <ze...@google.com> #4Jun 30, 2023 08:56AM

ku...@gmail.com <ku...@gmail.com> #5Jun 30, 2023 09:23AM

ze...@google.com <ze...@google.com> #6Jun 30, 2023 10:34AM

mk...@google.com <mk...@google.com> #7Jul 4, 2023 10:35AM

ku...@gmail.com <ku...@gmail.com> #8Jul 6, 2023 01:28PM

mk...@google.com <mk...@google.com> #9Jul 6, 2023 01:29PM

ap...@google.com <ap...@google.com> #10Jul 7, 2023 10:01AM

ap...@google.com <ap...@google.com> #11Jul 7, 2023 10:01AM

ap...@google.com <ap...@google.com> #12Jul 11, 2023 01:10PM

ap...@google.com <ap...@google.com> #13Jul 11, 2023 01:10PM

ap...@google.com <ap...@google.com> #14Jul 11, 2023 01:10PM

ap...@google.com <ap...@google.com> #15Jul 12, 2023 10:35AM

ap...@google.com <ap...@google.com> #16Jul 12, 2023 10:35AM

ap...@google.com <ap...@google.com> #17Jul 12, 2023 10:35AM

mk...@google.com <mk...@google.com> #18Jul 12, 2023 01:21PM

mk...@google.com <mk...@google.com> Jul 14, 2023 07:33AM

vl...@gmail.com <vl...@gmail.com> #19Jan 23, 2024 10:45AM

ze...@google.com <ze...@google.com> #20Jan 23, 2024 12:07PM

Add comment

Issue metadata