e.startsWith is not a function

My contact has recently reset his keys.

I saw the notice of that in our chat and, after clicking Jump to new conversation nothing was happening (or it looked like so), so I clicked again a couple of times and then this error appeared at the top of the Keybase client window.

TypeError: e.startsWith is not a function at Object.m [as isPendingConversationIDKey] (file:///Applications/Keybase.app/Contents/Resources/app/desktop/dist/index.bundle.js:1:205342) at d (file:///Applications/Keybase.app/Contents/Resources/app/desktop/dist/index.bundle.js:6:82435) at d.next (<anonymous>) at n (file:///Applications/Keybase.app/Contents/Resources/app/desktop/dist/index.bundle.js:6:162150) at s (file:///Applications/Keybase.app/Contents/Resources/app/desktop/dist/index.bundle.js:6:167747) at k (file:///Applications/Keybase.app/Contents/Resources/app/desktop/dist/index.bundle.js:6:163838) at x (file:///Applications/Keybase.app/Contents/Resources/app/desktop/dist/index.bundle.js:6:164445) at y (file:///Applications/Keybase.app/Contents/Resources/app/desktop/dist/index.bundle.js:6:163393) at file:///Applications/Keybase.app/Contents/Resources/app/desktop/dist/index.bundle.js:6:165943 at Array.forEach (native)

Start with the reported desktop bundle at Applications/Keybase.app/Contents/Resources/app/desktop/dist/index.bundle.js and the isPendingConversationIDKey stack entry, then trace it back to the corresponding client source. Reproduce the key-reset notice flow by clicking “Jump to new conversation”; done means the navigation works without the TypeError.