All four E2E legs failed to resolve :app:connectedDebugAndroidTest:
Could not find com.google.testing.platform:android-device-provider-local:0.0.9-alpha04
That is AGP's Unified Test Platform, the thing that actually runs instrumented
tests, and the guard added two commits ago was rejecting it. The guard was
written as a blanket rule over every configuration, and AGP resolves its own
tooling through this project's configurations.
There is no stable version to move to, and there never has been: every module in
com.google.testing.platform has only -dev and -alpha releases, going back to
0.0.1-dev. Nor is the version ours to choose -- AGP 9.3.1 pins it through
com.android.tools.utp:android-test-plugin-host-additional-test-output:32.3.1. So
an allowlist entry would have been the first of several, one per prerelease tool
AGP happens to depend on, discovered one red matrix at a time.
Scoping the guard to the groups this project actually floats fixes the class
rather than the instance. It also retires the detekt exception: we do not float
dev.detekt, so the guard now has no opinion about it, where before it passed only
because "alpha.6" has a dot the pattern missed.
Worth naming the shape of this bug, because it is the second time in this branch
that a change looked complete locally and was not. Nothing that runs without a
device resolves the UTP configurations -- unit tests, ktlint, detekt, lint,
assembleDebug and assembleRelease were all green while connectedAndroidTest could
not resolve at all. Verified now by resolving that exact configuration directly,
and by confirming the guard still does its job: lifecycle 2.+ resolves to 2.11.0,
not 2.12.0-alpha01.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
JMR-devandClaude Opus 5
3c7b4b9063