TrustedPeersHelper quit unexpectedly. Catalina 10.15.7 (19H1615)

Yes, I did…eventually, thanks. It didn't work the first 3 times, but ultimately it did: I typed "tpctl reset" in Terminal, and once it succeeded, there were no more unexpected quit messages. Maybe it worked because I started in Safe Boot (holding shift key at startup).

Just typing "tpctl" gets an explanation which says that "tpctl reset" resets Cuttlefish for this account, whatever that means.

What I did was: booted in safe mode, log into iCloud (because I was logged off), type "tpctl reset" a few times as the first time I got an error, after it said reset complete I booted in normal mode and the issue was fixed. I hope this works for you too.

https://discussions.apple.com/thread/250775689

I have the same issue. I was forced to disable iCloud as "report crash" was taking up a lot of my cpu.

Supposed solution if one takes the time to explore this link https://discussions.apple.com/thread/250775689

Yeah, I saw that too, but it didn't help. I think one of these is the culprit, based on timing:

2021-12-14 macOS Catalina Security Update 2021-008 (10.15.7)

2021-12-14 Device Support Update (1.0.0.0.1.1632960232)

Gib Henry wrote:

Yeah, I saw that too, but it didn't help. I think one of these is the culprit, based on timing:

2021-12-14 macOS Catalina Security Update 2021-008 (10.15.7)

2021-12-14 Device Support Update (1.0.0.0.1.1632960232)

Is related to iOS apple iDevices

I have the identical problem. The task Trustedpeershelper crashes with segmetation-fault (sigsegv) after 0-1 sec. and is restarted every 10 seconds by Launchd.

First level support unfortunately only solves problems that you can solve yourself by 2sec Google research. An escalation towards 2nd or 3rd level does not take place.

Here, Apple seems to have concentrated solely on sales, not quality, which suggests to me to turn away from Apple in the future and turn to Linux alone, as I have been doing in parallel for years. The "tips" of the 1st level support are not helpful, if not even dangerous, because they recommend resetting the keychain, although I had reported extensively that this error pattern also occurs identically with a freshly installed 10.15.7 incl. patches.

Yes, I believe the security update was indeed the problem. Let's hope Apple issues a fix soon, it's driving me nuts!

did you find a solution?

I tried tpctl but get Error: 4099

Thanks, it worked!

I also have this problem with a freshly installed 10.15.7.

Therefore, I think it is unlikely that a "tpctl reset" can generally provide a remedy.