Indeed, per-above I was being stupid about something and have solved this problem. Learning: based on value of keys like com.apple.security.application-groups, assorted state is written to ~/Library. correcting a typo in a file like FruitBasket.entitlements results in there being both the new updated state in ~/Library and the old incorrect state the fileproviderd appears to cache some of this state and as a result: Provider registers itself under a new updated name for its XPC service end point while fileproviderd keeps on trying to connect to the original (incorrect) XPC service end point deleting all the invalid state from ~/Library and restarting fileproviderd corrected the issue.