Keybase Finder Integration refuses to load in MacOS 27.0 Beta (26A5368g)

[benrfairless]

Describe the bug
Enabling Keybase Finder integration in MacOS 27.0 Beta (26A5368g) generates an error, and the Keybase file system is not exposed.

To Reproduce
Steps to reproduce the behavior:

1. Ensure you are running MacOS 27.0 Beta (26A5368g)
2. Navigate to Settings > Files > Enable Finder Integration
3. Follow the instructions to enable kernel extensions
4. Restart the Mac twice to confirm the extensions are enabled.
5. Restart the Keybase application

Expected behavior
Keybase Finder integration should be possible when running Keybase for Mac.

Screenshots
The exact error message is:

We were unable to load KBFS (Fuse kext). This may be due to a limitation in MacOS where there aren't any device slots available. Device slots can be taken up by apps such as VMWare, VirtualBox, anti-virus programs, VPN programs and Intel HAXM.

Please run keybase log send to report the error.

I have run keybase log send. my log id: b5b67a3156c6bf8c106e5e1c

Additional numbers
The number 345567

[shallax]

Ahh, the annual "will Keybase actually get their act together and make this work before the new MacOS reaches release date?"

[benrfairless]

Ahh, the annual "will Keybase actually get their act together and make this work before the new MacOS reaches release date?"

I've moved our workloads away from Keybase because of this shrug

[kg4zow]

Given Keybase's past history of not even looking at the macOS beta versions ahead of time, my guess is that we'll have at least a few weeks during with Keybase just plain won't work on macOS 27.

If only Keybase/Zoom would spend the time figuring out how to write a macOS File Provider instead of relying on a kernel extension, especially since Apple has already announced that kernel extensions are deprecated, and will be removed in "some future version".

FWIW, I remember I also had trouble with the same error message when I upgraded to macOS 26. I forget the specifics, but I remember having to reboot a few times, and I remember having to manually give something permission that it didn't have, under "System Settings → Privacy & Security".