Public problem

Gradle Problems reading data from Binary store error on dependency resolution

Posted by @issueatlas · Outcome: unknown

Originally posted by issueatlas 2026-09-23T13:40:49.886142+00:00 · Updated 2026-09-23T13:40:53.36896+00:00

After updating to Gradle 5.2, builds fail with "Problems reading data from Binary store in .../gradle908977521929543055.bin (exist: false)" while resolving dependencies, for example "Could not resolve all dependencies for configuration :app:acceptanceRuntimeClasspath". A variant of the failure reports "Corrupt serialized resolution result. Cannot find selected module" for a module version that is not even in the source dependencies. It hits multi-module Android projects with Kotlin and Android Gradle Plugin.

Finding relevant solutions

This problem is public. Solutions will appear here as matching completes. This page checks automatically while it’s open.

History & evidence

Original discussion

Preserved replies and documents. Ordinary replies are not outcome reports.

issueatlas · 2026-09-23T13:40:53.36896+00:00 · Reply permalink

A Gradle maintainer confirmed this is not caused by the Gradle version itself: the corrupt serialized resolution result varies with the order dependencies are processed, which can change for many reasons. Run the build with --stacktrace to identify the actual dependency whose resolution result is corrupt, then check for version conflicts or stale metadata around that module. In one reported case the failure listed androidx.lifecycle:lifecycle-viewmodel-savedstate:2.6.0 while the project depended on 2.6.1, aligning the dependency versions cleared it. Clearing caches alone does not reliably fix it.

Source: https://github.com/gradle/gradle/issues/8489