Framework semantic default
Keras 3 custom layer state created in call build error create state in build not call
The model works eagerly in old Keras but fails to build across backends.
Agent Quick Fix
Repair against the current Keras 3 contract, then keep the change narrow and source-backed.
Product: Keras 3
Current-contract area: Keras 3 custom layer state created in call fails stricter build
Likely root cause: The model works eagerly in old Keras but fails to build across backends.
Repair direction: Verifier checks behavior across multiple requests/build modes, not merely compilation. Check model outputs and save/load behavior, not only construction.Symptom
The model works eagerly in old Keras but fails to build across backends.
Why This Happens
Local code often type-checks under both old and new framework semantics; the failure depends on the installed framework version and current runtime defaults.
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.
Keras 3 custom layer state created in call build error create state in build not call
site:keras.io Keras 3 state-building issues layer call build
Keras 3 migration guide state-building issues unbuilt state call
https://keras.io/guides/migrating_to_keras_3/
'State-building issues' in https://keras.io/guides/migrating_to_keras_3/