macOS Ventura "Family" app persistent store service log entries (sandbox)

Question

Level 1

22 points

macOS Ventura "Family" app persistent store service log entries (sandbox)

I am experiencing several errors in the console related to persistent store service connection, and I would appreciate some guidance on how to resolve them. Here are the errors that I am seeing repeating in the console log of my device:

error	10:31:05.786761+0100	Family	Persistent store service connection invalidated: failed at lookup with error 159 - Sandbox restriction
error	10:31:05.786854+0100	Family	Error communicating with persistent store service proxy: Error Domain=NSCocoaErrorDomain Code=4099 "The connection to service named com.apple.contactsd.persistence was invalidated: failed at lookup with error 159 - Sandbox restriction." UserInfo={NSDebugDescription=The connection to service named com.apple.contactsd.persistence was invalidated: failed at lookup with error 159 - Sandbox restriction.}
error	10:31:05.786890+0100	Family	Error connecting to remote endpoint: (null)
error	10:31:05.786941+0100	Family	fault: Unable to create token NSXPCConnection.  NSXPCStoreServerEndpointFactory 0x15766b710 -newEndpoint returned nil
fault	10:31:05.787048+0100	Family	CoreData: Unable to create token NSXPCConnection.  NSXPCStoreServerEndpointFactory 0x15766b710 -newEndpoint returned nil
error	10:31:05.787663+0100	Family	error: Failed to create NSXPCConnection
error	10:31:05.787934+0100	Family	Persistent store service connection invalidated: failed at lookup with error 159 - Sandbox restriction
error	10:31:05.787983+0100	Family	Error communicating with persistent store service proxy: Error Domain=NSCocoaErrorDomain Code=4099 "The connection to service named com.apple.contactsd.persistence was invalidated: failed at lookup with error 159 - Sandbox restriction." UserInfo={NSDebugDescription=The connection to service named com.apple.contactsd.persistence was invalidated: failed at lookup with error 159 - Sandbox restriction.}
error	10:31:05.788217+0100	Family	Error connecting to remote endpoint: (null)
error	10:31:05.788264+0100	Family	fault: Unable to create token NSXPCConnection.  NSXPCStoreServerEndpointFactory 0x15766b710 -newEndpoint returned nil
fault	10:31:05.788681+0100	Family	CoreData: Unable to create token NSXPCConnection.  NSXPCStoreServerEndpointFactory 0x15766b710 -newEndpoint returned nil

I'm not sure what is causing these errors, but they seem to be related to a sandbox restriction. Can you please advise me on what steps I can take to resolve these issues? Any help you can provide would be greatly appreciated.

Thank you in advance for your assistance.

Mac Studio, macOS 13.2

Posted on Feb 22, 2023 2:18 AM

Reply

Answer 1

Negsdvs

Level 1

8 points

Oct 19, 2023 5:05 AM in response to JeffreyPhD

Same problem here (Ventura 13.5.2/ Mac Mini M2)...

I'm seeing strange behavior in the user interface, i.e. unable to right click, wallpaper went to default, desktop icons are hidden and are "stuck" in that mode...

Tried turning off my location sharing with family members, terminating processes in Activity Monitor, and lots of other things... restarting...

So... will upgrading to Sonoma help?

Reply

Answer 2

Orj

Level 1

66 points

Nov 4, 2023 9:54 AM in response to _Gu

Seemed to work for me... until I restarted sidecar (which times out after a couple of minutes, this being the reason for me to look at the console...). With ipad screen used as extended monitor via sidecar, I get ~12 faults/s with

Family (CoreData) CoreData: Unable to create token NSXPCConnection.

and a little less than 5-10 faults/second with

imagent (CoreData) CoreData: Unable to create token NSXPCConnection.

Reply

Answer 3

Nov 23, 2023 12:08 PM in response to _Gu

I tried your advice and added a firewall rule. But My firewall is always closed. I tried to kill the process of family on terminal screen. After 30 minutes it was reborn.

macOS version: Ventura 13.6.1

I also checked console on my friends Mac Pro. He is working on Sonoma 14.1.1 version of macOS. He has same faults. But he didn't have any performance problem.

I hope someone find a better solution.

Reply

Answer 4

stunpix

Level 1

8 points

Nov 30, 2023 2:38 AM in response to _Gu

UPD: logs are back, so it doesn't work 😔

Surprisingly, a trick with IMCore.framework/imagent.app helped me! My firewall was disabled, but I enabled it, added imagent.app to the list of firewall exceptions, then removed it, and disabled the firewall again, and the issue is gone. I don't understand how that worked, but the log is clear now from these messages.

Reply

Answer 5

_Gu

Level 1

9 points

Nov 30, 2023 4:22 AM in response to Warloxk

Also some kind of update from me. I was the one telling about the firewall part. It is also back for me after like a day or so. Even though before I tried and used the service for iMessage for instance, and that day there were no errors.

I completely reinstalled MacOS from a backup and the same problems happen.

After that I did a complete clean install (removing all partitions and then letting the installer make new ones). After that I was of course back on the last MacOS version (MacOS 13.something). I don’t know the exact build number, but still the same issues. The errors are still there, but I think the performance is a normal (I think).

It has to be somewhere else right? My network maybe? DNS server? My Apple ID? Or we can look into on what hardware it happens.

I have a 13 inch M2 MacBook Air with 1TB storage and 8GB memory.

Reply