Error in Keybase SigChain preventing Login

Hey all, I've recently been unable to do many things in Keybase, this includes but is not limited to: logging in, retrieving files, cloning repos, and accessing my Stellar wallet.

I finally figured out something was wrong after getting my new phone and trying to sign in to my account. Upon attempting to log in I get the following message from the iOS App, `Message wasn't signed. Error code 218: GENERIC in method keybase.1.login.login`. I wanted to see if this was reproducible on [one of my laptops](https://keybase.io/king/sigchain#6debef5eafaf825f8026b93527bfb7f5b06ec0a31a3e668ae143ed4713af97a00f) so I logged out using the macOS GUI, tried to log back in, and got the exact same error.

After that I started to do some digging and found https://github.com/keybase/client/issues/3064 and https://github.com/keybase/client/issues/5378 which seemed to be the exact issue that I was having. I tried the following the recommendation other issues in that issue to to run `keybase db nuke` and that did not help my login errors.

Next I tried to force a login using the `--paperkey` flag and I had the same results:

```
$> keybase login --paperkey="f..."
▶ ERROR Message wasn't signed
```

Anyone will be able to reproduce this error if they even run `id` on my user:
```
$> keybase id king
▶ ERROR Message wasn't signed
```

If anyone has any tips on how to unfuck my SigChain I would love to hear them. Thanks!

Start by reproducing the failure with `keybase id king`, `keybase login --paperkey`, and the iOS or macOS login flow. Read the linked issues 3064 and 5378 alongside the reported SigChain entry, then trace the `Message wasn't signed` error. Done means login, identity lookup, file or repository access, and Stellar wallet access no longer fail for this account.

Written by the indexing model from the issue text.