Keybase requires reprovisioning after update?

Hi,

I used keybase a while ago on my machine (around December last year) got it all set up and working - great.

Went to play with it again today and it says I need to login on the device again, but logging in complains that I can't reuse the same Device name.

Looking in the ~/.config/keybase dir, I have:

-rw------- 1 shane shane 290 Dec 16 2015 config.json.########################
-rw------- 1 shane shane 1380 Dec 16 2015 secretkeys.dataforce.mpack

Where the ######################## is a random-looking ID so I've masked it here for now. Of note is that there doesn't appear to be a config.json file without the random extension.

Looking in that file, there is a user section with a "device" and a device id - though this doesn't appear to match the device ID used in the "device remove" example at https://keybase.io/dataforce/devices ?

Given that this device hasn't been reinstalled and the .config/keybase directory hasn't changed i'm curious as to what has happened here and why this device no longer seems to think it is linked to my account, and also how I can go about resolving this (Trying to re-add it complains that the device name is already in use, which is True, but it's the same device)

Thanks,

• Shane

Start by reviewing the reported ~/.config/keybase/config.json.######################## and secretkeys.dataforce.mpack files, then compare their device information with the device-remove example linked in the issue. Reproduce the login and device-name conflict if possible; done means the cause of the lost device linkage and a verified recovery path are documented or fixed.