SDK bundle/module removal
Firebase Android BoM KTX libraries removed main modules package relocation unresolved imports
The separate artifact is removed, but blindly deleting it leaves unresolved imports until the correct main module/API is used.
Agent Quick Fix
Repair against the current Firebase Android contract, then keep the change narrow and source-backed.
Product: Firebase Android
Current-contract area: Clean BoM upgrade exposes main-module KTX package relocation
Likely root cause: The separate artifact is removed, but blindly deleting it leaves unresolved imports until the correct main module/API is used.
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
The separate artifact is removed, but blindly deleting it leaves unresolved imports until the correct main module/API is used.
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 libraries removed main modules package relocation unresolved imports
site:firebase.google.com/docs/android BoM 34.0.0 KTX libraries removed Firebase Android
Firebase Android KTX modules removed July 2025 BoM 34.0.0
https://firebase.google.com/docs/android/kotlin-migration