Bug Report for "Records are not supported" Issue in Android Instrumentation Testing
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- android, java
- Domain
- mobile-dev, testing
Research direction
Start by reproducing the Android instrumentation test failure using the environment details in the report: Android Studio Giraffe, Java 11, SDK 33, and the stated Android Gradle Plugin and Gradle versions. Check the instrumentation-test setup and build configuration for the reported R8 “Records are not supported” error; done means identifying a reproducible cause and confirming that the tests run successfully without it.
Written by the indexing model from the issue text.
Description
Issue While Runnig Intrumentation Test : com.android.tools.r8.internal.YI0: Records are not supported
Description: I encountered an issue while running Android Instrumentation tests. The error message I received is as follows:
com.android.tools.r8.internal.YI0: Records are not supported
This error is impacting the execution of my instrumentation tests and preventing them from running successfully.
Steps to Reproduce:
Set up an Android project with instrumentation tests.
Configure and run the instrumentation tests using the required setup.
Observe the mentioned error message during the test execution.
Expected Result:
The instrumentation tests should run without encountering the "Records are not supported" error.
Actual Result:
The error "com.android.tools.r8.internal.YI0: Records are not supported" occurs during the test execution, causing the tests to fail.
Environment:
Android Studio version: Android Studio Giraffe | 2022.3.1 Patch 1
Android Gradle Plugin version: [Your AGP version](com.android.tools.build:gradle:3.6.4)
Java version: [Java 11]
Android SDK version: [33]
Gradle version: [3.6.4]
Additional Information:
Please let me know if there are any workarounds or solutions available to address this issue. If there are any further details required from my end to investigate or resolve the problem, please inform me.
Recommended warning:
We recommend using a newer Android Gradle plugin to use compileSdk = 33
This Android Gradle plugin (7.1.3) was tested up to compileSdk = 32
This warning can be suppressed by adding
android.suppressUnsupportedCompileSdk=33
to this project's gradle.properties
The build will continue, but you are strongly encouraged to update your project to
use a newer Android Gradle Plugin that has been tested with compileSdk = 33
Link to a public git repo demonstrating the problem:
Thank you in advance 🙏
- Dominant language
- Java
- Stars
- 1.2k
- Forks
- 342
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 5
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from android/android-test
-
Difficulty 1/5 Under an hour Newbie friendliness 62/100
android/android-test#681 · 2 comments · 1 reaction ·
-
Difficulty 3/5 1-2 days Newbie friendliness 72/100
android/android-test#2507 · 1 comment ·
-
ξεκσνδξδ Open
Difficulty 5/5 Over a week Newbie friendliness 1/100
android/android-test#2499 ·
-
ησξξσ Open
Difficulty 5/5 Over a week Newbie friendliness 1/100
android/android-test#2498 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 38/100
android/android-test#2473 ·
All issues in android/android-test
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
elastic/gradle-plugins#157 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
cryptomator/hub#497 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
johanhaleby/occurrent#1120 ·