The tests for the briar-android module use a cached version of the bramble-android AAR, which may be stale. They should use the AAR created by the bramble-android module during the same build.

On my system the cached AAR is loaded from ~/.gradle/caches.

The issue is visible when changing between branches where the Dagger modules exposed by bramble-android have changed. For example, try adding an argument to AndroidPluginModule#providePluginConfig(), running the tests, then switching to a branch that doesn't have the change and running the tests again.

Running gradle clean doesn't help, perhaps because the cached AAR is outside the build directory.

!666 (merged) was an attempt to fix this, but it doesn't seem to have worked.

We've had issues in the past with Briar releases including stale versions of Bramble. Could that have been caused by the same issue?