@@ -15,8 +15,9 @@ Note in particular that **extensions must be bundled inside another application*
1515 ```
1616
17172. Navigate to ` System Settings > General > Login Items & Extensions` , and scroll down to the Extensions section.
18- - Opening the link ` x-apple.systempreferences:com.apple.LoginItems-Settings.extension` should do the trick.
19- - In the File System Extensions cell, click the ⓘ symbol, and enable " FSKit Example Extension" .
18+ - (Opening the link ` x-apple.systempreferences:com.apple.LoginItems-Settings.extension` should do the trick).
19+ - On macOS 26, click ` By Category` .
20+ - In the ` File System Extensions` cell, click the ⓘ symbol, and enable " FSKit Example Extension" .
2021
21224. Create a directory to serve as the mount target for the file system:
2223 ` ` ` sh
@@ -39,7 +40,7 @@ Note in particular that **extensions must be bundled inside another application*
3940
40416. Optional: In another terminal, tun the following to get the logging output:
4142 ` ` ` sh
42- /usr/bin/log stream --predicate ' subsystem = "fskit-example"' --style compact --level debug
43+ /usr/bin/log stream --predicate ' subsystem == "fskit-example"' --style compact --level debug
4344 ```
4445
4546 See [` println! ` debugging](# println-debugging) below for details.
@@ -118,7 +119,7 @@ Writing to `/tmp` files won't work either, as those are sandboxed away too.
118119
119120Instead, we use `tracing-oslog` to log errors via Apple' s OSLog. These can be viewed with:
120121` ` ` sh
121- /usr/bin/log stream --predicate ' subsystem = "fskit-example"' --style compact --level debug
122+ /usr/bin/log stream --predicate ' subsystem == "fskit-example"' --style compact --level debug
122123` ` `
123124
124125That said, I _have_ seen it fail at the boundaries / entry/exit points (` deactivateWithOptions:replyHandler:` for example isn' t logged IIRC), so it' s not a perfect solution.
0 commit comments