SDK bundle/module removal
Firebase Android BoM KTX artifact removed firebase-remote-config-ktx release notes
Kotlin extensions vanish after BoM migration.
Agent Quick Fix
Repair against the current Firebase Android contract, then keep the change narrow and source-backed.
Product: Firebase Android
Current-contract area: Firebase Remote Config KTX artifact removed from BoM 34
Likely root cause: Kotlin extensions vanish after BoM migration.
Repair direction: Verifier checks the supported main-module API and dependency graph without reintroducing removed artifacts. Check the resolved dependency graph and runtime behavior on the declared minimum platform.Symptom
Kotlin extensions vanish after BoM migration.
Why This Happens
A BoM or aggregate package can stop publishing modules while source imports still look correct and old caches continue to mask the break.
Common Wrong Fixes
- Changing local code without checking the current external contract.
- Retrying the same install, build, or API call with no version/source change.
- Applying a broad unsafe bypass when a narrow compatibility fix is available.
Codex Search Keywords
These are the search terms observed in a neutral Codex validation run for this failure shape.
Firebase Android BoM KTX artifact removed firebase-remote-config-ktx release notes
site:firebase.google.com/docs/android/kotlin-migration firebase-remote-config-ktx BoM 34
Firebase Android SDK release notes BoM 34.0.0 ktx
Firebase KTX APIs have been added to the main modules July 2025
https://firebase.google.com/support/release-notes/android
https://firebase.google.com/docs/android/kotlin-migration