Keybase throws track error when friend changed his key.

Hi,

A few weeks ago I had to change my key and push them to keybase. There is no problem thus far..

The main reason for what we use Keybase is to make key sharing easy and managable. However after I changed my keys and asked my friend to refresh (pull) their list, they received an error says that:
"2018-10-03T13:33:35.818522+03:00 - [WARN keybase log_ui.go:36] 010 Keybase says that ziyahan owns key fc8ef5e568350fb6357287e7bc7829cc3574089e, but you have not tracked this fingerprint before. [tags:ENG=XaToxD4mfA6w]"

and could not update my public key in their list. If and only after the unfollowing and then following me, they can update their list with my new key.

It is very weird.

Could you explain why it happened and whether it is expected behavior? It seems a bug.

Thanks in advance.

Start with the warning reported from log_ui.go:36 and trace the track and refresh flow described in the issue. Reproduce changing a user's key, then have a friend refresh the list and compare it with unfollowing and following again. Done means the behavior is explained and, if it is a bug, the friend can update the key through refresh without that workaround.

Written by the indexing model from the issue text.