Unexpected Remoted crash report appearing on MacBook Pro

frets wrote:

From out of nowhere I started getting a crash report from Remoted. The Mac acted normally. I don't use any remote apps. The message appears in Safari, Firefox, Duck Duck go and Chrome. This morning it was open by itself when I opened the Mac. It bugs me! I've quoted the top of the message.

Thenks for any info you can share.

Frets

2019 MacBook Pro

OS 26.2

https://discussions.apple.com/content/attachment/55feb541-3bc6-4c78-8195-779d5bdade76

I never saw a associated "crash report," as you implicate—

however I was seeing a "Problem Report" which appeared on Intel Macs with the 26.2 point-update

which could be dismissed or Send to Apple

The recent point-update 26.3 seems to have resolved the issue....

The current stable release of Tahoe including bug fixes, security updates is macOS 26.3

Keep your Mac up to date - Apple Support

Keep your Mac up to date - Apple Support

report back your success or failure....

William Tyson wrote:

Similar problem reports about Remoted are showing up on a MacBook running 26.3.1 (continuing after a reboot)

MacBook Pro 13-inch 2020 Intel

A watchdog checkin with service remoted returned not alive.., 85 seconds since last successful checkin. 1126 total successful checkins since 1428 seconds ago. Uptime 14000

Yeah, yeah, 26.3.1 is 40 days old so of course there are two more updates since then.

?

I don't get it.... why make this post if you are unwilling to stay current with bug fixes

current release of Tahoe is macOS 26.4.1

Keep your Mac up to date - Apple Support

Keep your Mac up to date - Apple Support

if no resolve then report back.

<< I post bugs not to be told "update to this week's release" but hopefully to find someone that has found a cause ("I found that the xyzzy app was causing this") or a work-around ("turn off Apple's configuration X") ,,, >>

When the volunteer readers here recognize that as an issue seen before, then recognition that this has been seen before, and any details of any known work-arounds would have been provided to you in excruciating detail by multiple readers. Some have referred to this as the "Pit Crew" effect, where you are swarmed with that information from all sides.

At this writing, this discussion topic has 335 reads and six replies.

'That you did not get swarmed' confirms that Readers do not recall seeing anything like your issue before.

Coming from here, suggesting that you update to the current release is not just putting you off. No one wants to debug a problem that has already been seen and solved. In addition, when you contact support, that is one of the very first things they will require of you. So doing that update before you call them will avoid delays.

<< (perhaps as a fantasy) that Apple might recognize that people are complaining about a bug, up its priority, chase it down, and fix it. >>

It's not a fantasy, but that mechanism is NOT these User-to-User support communities. Apple employees (with the exception of forum moderators) are prohibited from posting here, so they generally do not READ here either. If you want to get your complaint before an Apple employee, you can drop a reply in the Product Feedback Drop Box:

Product Feedback - Apple

Similar problem reports about Remoted are showing up on a MacBook running 26.3.1 (continuing after a reboot)

MacBook Pro 13-inch 2020 Intel

A watchdog checkin with service remoted returned not alive.., 85 seconds since last successful checkin. 1126 total successful checkins since 1428 seconds ago. Uptime 14000

Yeah, yeah, 26.3.1 is 40 days old so of course there are two more updates since then.

William Tyson wrote:

Updating is not zero cost. It takes time and loses the state of the user's use of his machine. It introduces a risk that the update may break something the user depends upon.

Simply saying "Update and report back" is much the same as a MD saying "Take two aspirin and call me in the morning." It provides no explanation of cause nor any suggestion of resolution.

you can Call Customer Support  (800) MY–APPLE (800–692–7753) let them drill down on your on-going issue.

or on line  https://getsupport.apple.com/

Outside the USA—Contact Apple for support and service by phone

See a list of Apple phone numbers around the world.

Contact Apple Support - Apple Support 

The claim above that updating to 26.3 would fix the issue was exaggerated (apologies to Mark Twain). My post was to confirm the same or similar bug was happening in 26.3.1 (so, unless the issue was re-introduced in 26.3.1, it seemingly wasn't fixed in 26.3).

I don't get your confusion. I post bugs not to be told "update to this week's release" but hopefully to find someone that has found a cause ("I found that the xyzzy app was causing this") or a work-around ("turn off Apple's configuration X") or (perhaps as a fantasy) that Apple might recognize that people are complaining about a bug, up its priority, chase it down, and fix it.

Nothing in Apple's Release Notes for Tahoe 26.3 or 26.4 or 26.5 Beta 4 mention anything about remoted or watchdog processes or anything related (processes that get blocked, etc). If you can point me to a specific resolved issue that resolves this, that would be great. Heck, I'd be happy if you can show me a known issue that would indicate Apple has this on their radar. I didn't see one.

Updating is not zero cost. It takes time and loses the state of the user's use of his machine. It introduces a risk that the update may break something the user depends upon.

Simply saying "Update and report back" is much the same as a MD saying "Take two aspirin and call me in the morning." It provides no explanation of cause nor any suggestion of resolution.