# Gradle Problems reading data from Binary store error on dependency resolution
## What's going on
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.
## The verified fix
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
## How to use this
Take the question above and check if it matches what you're seeing. If it does, work through the verified fix step by step. Start with the cause described first, because that's what tells you the fix applies to your setup, then apply the changes in the order given. Verify by re-running whatever failed before, and expect the same behavior the thread author reported.