What’s Changed
- Bump the Bitrise Build Cache CLI to v3.8.4. Gradle activation now persists the credential it resolves, so the Gradle plugins can still authenticate when the build runs in a later step. Since v3.8.1 the plugins resolve their own token by running the CLI mid-build rather than reading one from the init script; on CI where the credential is scoped to the activation step — the usual shape on GitHub Actions — the build had no token to find and analytics uploads were rejected with
Unauthenticated. React Native activation shares that Gradle activation path, so its Android builds get the fix. Builds on Bitrise were unaffected, because the per-build JWT is present in every step. - Also picks up v3.8.3: Gradle builds print a cache and a task summary at the end of the build, the task hit rate the Build Cache UI shows was too low and is now correct, and a colourised auth token no longer breaks Gradle analytics.