Every topic below maps one symptom to its likely cause, and links to the version or compatibility guide that explains the underlying relationship. The general principle is the same throughout: work from the error backwards to the layer it names, and change one thing at a time.
Why not “just replace the keyset”
Replacing files is the most common approach and the least informative one. It discards the evidence the error was providing and often introduces a new variable. If a mismatch is reported at a specific layer, that layer tells you which of the four elements in the compatibility chain is out of step.
Before anything else
- Confirm the filename and location match what the tool expects.
- Confirm the keyset is the unmodified original, not a copy that has passed through an editor.
- Read the error text literally — the layer it names is the layer to investigate.
- Check the versions hub for whether the revision you have has been confirmed on this site.
The topics
Each page follows the same structure: the symptom, the likely causes in order, how to confirm which one applies, and where the underlying relationship is explained. Where a cause relates to a recorded value that has not been confirmed, the page says so rather than inventing one.