IssueTracker

Thank you for posting an issue. It is not obvious to me what the error is, please give some more information, ideally a dump that would allow me to reproduce the issue locally.

If you cannot provide a dump, please share the full stack trace and potentially the classes that are failing if that is available from the information you have. You can probably obtain it by running the release process from the command line.

The Expected stack map table for method with non-linear control flow. is because you have invalid class file input. It is an error to not provide frame information in jumps and has been so from class file version 50.

If the issue re-appears feel free to re-open the bug.

The application I'm working on is getting the same error after upgrading Gradle and the Gradle Plugin (7.4.1). Very little info online about this. Let me know what info I can provide; it seems like a legitimate issue given that multiple people are reporting it.

The application I'm working on is not using androidx.multidex:multidex like the other user.

> Task :app:dexBuilderDebug FAILED
AGPBI: {"kind":"error","text":"com.android.tools.r8.internal.Fq: No VersionRequirement with the given id in the table","sources":[{}],"tool":"D8"}
AGPBI: {"kind":"error","text":"com.android.tools.r8.internal.Fq: No VersionRequirement with the given id in the table","sources":[{}],"tool":"D8"}
com.android.tools.r8.internal.Fq: No VersionRequirement with the given id in the table


Execution failed for task ':app:dexBuilderDebug'.
> Could not resolve all files for configuration ':app:detachedConfiguration3'.
   > Failed to transform jetified-anko-sdk25-coroutines-0.10.3.jar to match attributes {artifactType=ext-dex-dexBuilderDebug, org.gradle.libraryelements=jar, org.gradle.usage=java-runtime}.
      > Execution failed for DexingExternalLibArtifactTransform: /Users/.../.gradle/caches/transforms-3/17e3e87543b7bc6c15b2729175c4f93a/transformed/jetified-anko-sdk25-coroutines-0.10.3.jar.
         > Error while dexing.
   > Failed to transform jetified-anko-appcompat-v7-coroutines-0.10.3.jar to match attributes {artifactType=ext-dex-dexBuilderDebug, org.gradle.libraryelements=jar, org.gradle.usage=java-runtime}.
      > Execution failed for DexingExternalLibArtifactTransform: /Users/.../.gradle/caches/transforms-3/192f3b6aa3588ba73225fa6268e99efa/transformed/jetified-anko-appcompat-v7-coroutines-0.10.3.jar.
         > Error while dexing.

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.

com.android.tools.r8.internal.Fq: No VersionRequirement with the given id in the table

I've tried invalidating caches as well as rebuilding the project.

Please let me know if I should open a separate ticket!

Would it be possible to provide a dump or another reproduction? You can share it privately by sending it to mkroghj@google.com or sgjesse@google.com.

Potentially I only need /Users/.../.gradle/caches/transforms-3/17e3e87543b7bc6c15b2729175c4f93a/transformed/jetified-anko-sdk25-coroutines-0.10.3.jar to reproduce the problem.

Are you using desugared library? Is this R8 or D8 (minifyEnabled = true)?

https://r8.googlesource.com/r8/+/f87487f262227fe5a67ba8b8136bec7eacfe2279/tools/compiledump.py

I tried to look for the library for which the issue is reported adding the dependency implementation 'org.jetbrains.anko:anko-sdk25-coroutines:0.10.3' to a project. However that artifact is not found on the usual Maven repos, and https://mvnrepository.com/artifact/org.jetbrains.anko/anko-sdk25 has only one version. Also the Anko project has been discontinued. So making a reproduction seems unlikely. As Morten mentioned in comment #6 either a full dump or at least a copy of jetified-anko-sdk25-coroutines-0.10.3.jar will be needed to make progress.

The error is that old kotlin compilers would generate synthetic lambdas with version requirement: 0 as default but it actually should just be empty. An issue was reported on kotlin here: https://youtrack.jetbrains.com/issue/KT-29790.

This is fixed from 1.3.40-dev and forward. The synthetic lambda that fails has metadata version 1.1.15 and therefore compiled by a compiler that generated the invalid entry in version requirement.

We should not throw an error that fails compilation in D8. This is fixed ToT and I will cherry-pick to our release branches.

Our 8.0 branch corresponds to Android Studio Flamingo, and it should be in for the final release.

เรียนรู้แอนดรอยด์

This is fixed from AGP 8.0, so please ensure that version or higher is used.

I filed Issue 243705209 to track #17.

I've attached a project which demonstrates when a build will break in case (3) from #16.

In this project, the app gets its namespace ("com.example.namespace") from the package attribute of the AndroidManifest.xml.

The AndroidTest component gets its namespace from the testApplicationId, and it's the same namespace as the app's.

The AndroidTest component calls com.example.namespace.R.string.app_android_test_string in ExampleInstrumentedTest, which compiles as-is (./gradlew :app:assembleAndroidTest), but if we add namespace "com.example.namespace" to the DSL, then it doesn't compile anymore because the AndroidTest component's namespace becomes "com.example.namespace.test".

Thanks for the test project.

What are the downsides of preserving the workingness of the project by adding testNamespace "com.example.namespace" in the case that there is a collision, like in this test project? It builds successfully for me, but maybe there are subsequent problems?

If namespace == testNamespace, then ./gradlew :app:assembleAndroidTest should fail. See here

Thanks. (But not in the test project from comment#19 which uses AGP -alpha09).

Ah, yes, looks like that change was merged in -alpha10.

OK. I've implemented the behaviour in comment#16, except that in the case of colliding names between main and androidTest packages we block the upgrade rather than upgrade to something that doesn't work: largely because there's no real way at the moment to conditionally hook the post-upgrade display (given that the post-upgrade display absolutely must display sync status and rollback recommendations/suggestions if appropriate). I think this is probably best (and consistent with other upgrade processors).

I think that's it for Upgrade Assistant support on this, apart from the precise canary when the new behaviour is activated: over to you, Scott.

Thanks! Closing this bug as I still have Issue 200682321 open to track updating the precise canary version.

Is there a way to fix this?

Can you use the fully qualified name instead of ".TestApplication"?

If that doesn't work for you, can you give more details so I can reproduce the issue? IIUC, the actual fully qualified class name is com.myapp.android.TestApplication, and android:name=".TestApplication is located in the androidTest AndroidManifest.xml... is that correct?

Using fully qualified name fixes the problem, but it is not an elegant solution for a huge project with hundred of modules with android tests where it all needs to be fixed manually.

Unfortunately, I can't think of another way to fix the problem.

It worked well with "package" in Manifest.

Yes, but we've opted to (1) disallow setting a value for package that is different than the (test) namespace and (2) disallow having namespace match testNamespace. (1) - because it is confusing, and (2) - because there can be unintended collisions of production vs test android resources.

Very sorry for the breaking change.

Isn't this issue more related to the change we made to the test applicationID as part of this change? It used to be that the test appID was computed badly based on the test package, but we change the computation (I don't remember exactly the change).

The relative path in the manifest is expanded based on testApplicationId, not the testNamespace (computed or explicit).

You should configure this to be what you expect it to be.

The relative path in the manifest is expanded based on testApplicationId, not the testNamespace (computed or explicit).

That was the old behavior, but AGP uses the namespace now, not the application ID. See Issue 213474165.