MacOS KBFS Error
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
I installed Keybase and when I arrived at the point where I was setting up KBFS, I accidentally failed to unlock my Security & Privacy pane **before** I granted Keybase permission. This seemed to bork my KBFS implementation. I can see the `/keybase` directory but I'm not able to access it. When I try to access through the Keybase GUI, I'm continually presented with the red banner stating "Your Keybase folders are currently not showing up in your Finder."

Regardless of the number of times I click "Display in Finder", nothing happens. I've performed a complete uninstall of Keybase (`keybase uninstall`) and reinstalled from a fresh download, but I've never been presented again with the option to grant Keybase permission to my Mac.
I feel like the issue is rooted in my computer remembering prior permissions, and those permissions aren't sufficient to allow KBFS to function.
I've shuffled the permissions on my `/keybase` directory to try and get in that way, but so far, nothing has worked. When I install Keybase fresh, when I initially try to access my folders I'm presented with the following screen:

After I input my username and password, nothing else happens. I'm just continually informed that Finder cannot display my folders. If I run `keybase fs ls /keybase` I get an error saying `ERROR Invalid remote path`.
my log id: 81b2c2d54b0b0ec51f849f1c
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reproducing the macOS setup sequence, including the Security & Privacy permission step, then inspect the KBFS setup flow and the `keybase fs ls /keybase` entry point using log id 81b2c2d54b0b0ec51f849f1c. Done means the Keybase folders appear in Finder and `keybase fs ls /keybase` no longer reports `ERROR Invalid remote path`.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, macos
- Domain
- desktop, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100