We need file provider extension processes to talk to each other. What first appeared to be prevented by sandbox on iOS works with a different API.

Having a file provider extension with multiple domains and processes and even more enumerators logging in parallel can become a mess. Leveraging the subsystem and category fields to the rescue.

Apparently, the feature set of fileproviderctl has been narrowed down to the dismay of developers, testers and even administrators and it appears to be intentional.

Out of necessity I created a minimalistic SwiftUI app which performs MD5 hashing to get a rough feeling how efficient it is on Apple devices.

I need to maintain a virtual file system in a CoreData database. Setting up test scenarios is tiresome, so I made use of result builders and its nice.

There is a better way than to repeat the same or similar NSPredicate all the time and it is very nice to read.

I rarely need to use defer blocks and mostly it is for ending signpost intervals. I checked the possible situation of having multiple and in which order they are executed.

I was very excited about macros because they allow the reduction of boilerplate code like handling signposts. This macro reduces signposting in a method to a single word expression.

I found out how to successfully get replicated file provider services by URL on iOS which previously was impossible due to FileManager throwing a cryptic error.

This is one of the things I do not find when I am looking for them but only later by accident. When Xcode is reports warning with strict concurrency checks enabled and they are about Apple’s own frameworks, they might be what you are looking for.