r-zakarya
4d9fd2c34a
The except only covered decryption and the patch. An exception from re-encryption or from the PUT skipped the block that restores the screen - and that block also held the message, so the failure was invisible as well as permanent: the row stayed on "Saving..." with nothing to explain it. Restoring the screen now lives in the finally, so it happens whatever the code above did. A catch-all around the body turns any unforeseen exception into a message and a log line, because a failure that says nothing is indistinguishable from slowness - which is exactly how this one was reported. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
