Keychain lookups fail quietly instead of crashing, and unparseable config files now get reported.
What's wrong with this entry?
Reading credentials from the macOS keychain now returns nothing on failure instead of throwing or handing back a partial result when the lookup times out. Separately, a config file that fails to parse emits a tengu_config_parse_error event recording the file size, whether cached auth was available, and whether a timestamped backup exists.
- The keychain lookup runs
security find-generic-password; both a thrown error and a killed process now resolve to null. - The parse-error event is scheduled asynchronously and claimed once per file, so a failure reporting a failure cannot loop.
tengu_config_parse_error
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.234
Signing back into the same account keeps a pending auto-resume
Both mention auth
-
v2.1.234
Token screen reports actual remaining validity
Both mention auth
-
v2.1.234
Setup-token login result carries the expiry
Both mention auth