Minimum platform level
Firebase Android Crashlytics major version minSdk 23 release notes
Release build fails only after Crashlytics major upgrade.
Agent Quick Fix
Repair against the current Firebase Android contract, then keep the change narrow and source-backed.
Product: Firebase Android
Current-contract area: Crashlytics raises minSdk to 23
Likely root cause: Release build fails only after Crashlytics major upgrade.
Repair direction: Verifier checks an explicit product decision: raise the app floor with metadata/tests, or pin a still-supported SDK line. Check the resolved dependency graph and runtime behavior on the declared minimum platform.Symptom
Release build fails only after Crashlytics major upgrade.
Why This Happens
The source can compile on the developer's newer device while the SDK's newly raised deployment/minSdk target fails older build or runtime matrices.
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 Crashlytics major version minSdk 23 release notes
site:firebase.google.com/support/release-notes/android Crashlytics minSdk 23 19.0.0
Firebase Crashlytics Android SDK 19.0.0 minSdkVersion 23
https://firebase.google.com/support/release-notes/android
'minSdkVersion' in https://firebase.google.com/support/release-notes/android