Android Studio: Fix “Found interface … GradleBuildInvoker$Request, but class was expected”

Starting with Android Studio Panda 3 Canary 1, pressing Run can immediately fail with “Found interface … GradleBuildInvoker$Request, but class was expected.” Google’s known-issues page and public issue tracker identify an incompatibility between Android Studio’s changed internal API and Develocity IDE plugin 1.2.0.

The error
Cause
Affected versions and conditions
Recommended fix
1. Update the Develocity IDE plugin to 1.2.1 or later
Alternatives
1. Temporarily disable Develocity IDE plugin 1.2.0
2. Temporarily use a compatible Android Studio build
Verification
Cautions
Summary
Official references

The error

Found interface
com.android.tools.idea.gradle.project.build.invoker.GradleBuildInvoker$Request,
but class was expected

The IDE log can then contain entries such as:

Couldn't get post build models.
Gradle build failed

Cause

Android Studio Panda 3 changed the internal definition of GradleBuildInvoker.Request. Develocity IDE plugin 1.2.0 was compiled against the previous shape, producing an interface-versus-class mismatch at runtime. The app’s Kotlin source, AGP configuration, and Gradle cache are not the direct cause.

Google’s issue tracker records that Develocity IDE plugin 1.2.1 fixes the incompatibility, and the issue was marked Fixed on April 22, 2026. If the Android known-issues page still shows older temporary guidance, update to 1.2.1 or later first.

Affected versions and conditions

Android Studio Panda 3 Canary 1 or later is in use.
Develocity IDE plugin 1.2.0 is enabled.
A Gradle build is started with the IDE’s Run or Debug action.

The confirmed fixed release is Develocity IDE plugin 1.2.1. Updating Android Studio or AGP alone does not replace an installed IDE plugin that remains on 1.2.0.

Recommended fix

Update the Develocity IDE plugin to 1.2.1 or later

Open Settings in Android Studio, or Preferences on macOS.
Select Plugins and find Develocity under Installed.
Install the available update to version 1.2.1 or later.
Restart Android Studio.
Verify the plugin version and run the app again.

Alternatives

Temporarily disable Develocity IDE plugin 1.2.0

If the plugin cannot be updated immediately, open Plugins → Installed → Develocity, choose Disable, and restart the IDE. Google’s known-issues page lists this as the temporary workaround.

Temporarily use a compatible Android Studio build

This is a fallback when Develocity IDE integration is mandatory and the plugin cannot be updated. Install the older IDE side by side and keep its configuration directory separate.

Verification

Confirm that the Develocity IDE plugin is version 1.2.1 or later, or disabled.
Fully restart Android Studio.
Build and launch the app with the normal Run action.
Check Build Output and idea.log for the original diagnostic.
After updating, verify any required Build Scan or Live Build Timeline integration.

Cautions

The Develocity IDE plugin is separate from the Develocity Gradle plugin applied in a build script. This incompatibility concerns IDE plugin 1.2.0.
Deleting .gradle or Gradle caches is not the primary fix.
Disabling the plugin temporarily removes its IDE integration, but normal Gradle builds can continue.
If the exact diagnostic and stack trace differ, investigate another plugin conflict rather than assuming the same cause.

Summary

This error is caused by an incompatibility between an Android Studio Panda 3 internal API change and Develocity IDE plugin 1.2.0. Update the plugin to 1.2.1 or later. If that is not possible, disable 1.2.0 temporarily.