Missing keyset

Symptom: the tool reports that no keyset was found at all.

This is almost never a problem with the file’s contents. If a tool reports no keyset, it has not read one — so the cause lies in naming, location or configuration.

Likely causes, in order

1. Wrong filename. The file must be named exactly as expected, conventionally prod.keys. A renamed copy, a downloaded duplicate that gained a suffix, or a name with different capitalisation will all fail.
2. Wrong location. The application looks in one specific place. See emulator & frontend configuration for why this varies between applications.
3. Configuration not set. Where a path must be configured, an unset or stale path produces the same message as a missing file.
4. Hidden extension. A file saved as prod.keys.txt may display as prod.keys while remaining a text-extension file.

How to confirm

Copy the exact path the tool reports in its error, if it gives one, and check that a file exists at that path. If the tool gives no path, check the application’s documentation for its expected location, and verify the configured value if one exists.

Where this connects

Placement depends on the tool environment, so emulator & frontend configuration and keyset-aware desktop tools are the relevant tool pages. If the file is found but rejected instead, the problem is different — see tool cannot recognise keyset.