Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [BUG] Dispatch session wedged after April 28 app update; server-side pairing state stuck [2 comments, 3 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#55123•Fetched 2026-05-01 05:45:39
View on GitHub
Comments
2
Participants
3
Timeline
7
Reactions
0
Author
VissVissVissViss
Participants
github-actions[bot]github-actions[bot]PeltonPeltonVissVissVissViss
Timeline (top)
labeled ×5commented ×2

Error Message

Error Messages/Logs

Fix Action

Fix / Workaround

Dispatch session became permanently unresponsive after Claude Desktop auto-updated on April 28, 2026. Same symptom pattern as #52367.

  • Phone shows Dispatch as online and connected to desktop.
  • Sending a message from the phone: the "working on it" indicator activates immediately, sometimes before any message is sent.
  • Messages are received and marked as read.
  • No response is ever delivered to the UI on either desktop or mobile.
  • Standard Cowork sessions (non-Dispatch) work normally on the desktop.
  • Regular claude.ai chat works normally.
  1. Dispatch was working normally from April 23 through April 28.
  2. On April 28, Claude Desktop auto-updated.
  3. Active Dispatch session was wedged immediately on relaunch after update.
  4. Issue has persisted continuously since.
RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing issues and this hasn't been reported yet
  • This is a single bug report (please file separate reports for different bugs)
  • I am using the latest version of Claude Code

What's Wrong?

Dispatch session became permanently unresponsive after Claude Desktop auto-updated on April 28, 2026. Same symptom pattern as #52367.

Symptoms

  • Phone shows Dispatch as online and connected to desktop.
  • Sending a message from the phone: the "working on it" indicator activates immediately, sometimes before any message is sent.
  • Messages are received and marked as read.
  • No response is ever delivered to the UI on either desktop or mobile.
  • Standard Cowork sessions (non-Dispatch) work normally on the desktop.
  • Regular claude.ai chat works normally.

Sequence of events

  1. Dispatch was working normally from April 23 through April 28.
  2. On April 28, Claude Desktop auto-updated.
  3. Active Dispatch session was wedged immediately on relaunch after update.
  4. Issue has persisted continuously since.

Troubleshooting attempted

  • Quit and relaunched Claude Desktop multiple times.
  • Force-quit and relaunched the iOS app.
  • Toggled Dispatch off, hard-refreshed (Cmd+R), toggled back on.
  • Updated the iOS app to latest version.
  • Confirmed Claude Desktop is on latest version (1.5354.0).
  • Moved ~/.claude/bridge-state.json out of the directory and relaunched.
    • New session was created, but first message after the move also got stuck.
    • This indicates the broken state is server-side, not local.

Why I believe this is server-side

After moving bridge-state.json and forcing the app to recreate local state, the new session reproduced the exact same symptom on the very first message. Local state reset did not help. This matches the diagnosis in #52367: account-level Dispatch pairing state on the server has not recovered after an incident, and only Anthropic can reset it.

Environment

  • Plan: Max
  • Claude Desktop version: 1.5354.0 (9a9e3d), 2026-04-29T01:14:34.000Z
  • macOS: 26.3.1 (a) (25D771280a)
  • Hardware: MacBook M3 Pro
  • iOS device: iPhone 15 Pro Max
  • iOS version: iOS 26.4.2 (23E261)
  • Claude iOS app version: latest as of April 30, 2026

Related issues

  • #52367: identical symptom, server-side pairing state stuck
  • #45937: original "desktop appears offline" pattern from April 9
  • #49545: persistent Dispatch offline state
  • #40178, #40430: prior instances of "messages marked read, no response delivered"

Requested action

Please re-initialize the Dispatch pairing state on my account server-side. Client-side troubleshooting cannot resolve this. Happy to provide account ID, request IDs, or logs on request.

Impact

Dispatch is a primary reason I am on a paid plan. Losing this feature for multiple days with no resolution path significantly degrades the value of the subscription.

What Should Happen?

Dispatch should work!

Error Messages/Logs

Steps to Reproduce

It’s already explained above.

Claude Model

Opus

Is this a regression?

Yes, this worked in a previous version

Last Working Version

2 versions before 1.5354.0

Claude Code Version

N/A

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

No response

extent analysis

TL;DR

The most likely fix is to re-initialize the Dispatch pairing state on the user's account server-side, as the issue is believed to be caused by a stuck account-level Dispatch pairing state.

Guidance

  • The user has already attempted various client-side troubleshooting steps, including resetting local state and updating the iOS app, but the issue persists, suggesting a server-side problem.
  • The fact that moving bridge-state.json and recreating local state did not resolve the issue supports the diagnosis of a server-side issue.
  • To verify the issue, the user can try sending a message from the phone and check if the "working on it" indicator activates immediately, and if the message is received but not responded to.
  • The user should provide their account ID, request IDs, or logs to the support team to facilitate the re-initialization of the Dispatch pairing state.

Notes

The issue is similar to a previously reported issue (#52367), which suggests that the problem may be related to the server-side pairing state.

Recommendation

Apply workaround: Re-initialize the Dispatch pairing state on the user's account server-side, as this is the most likely solution to resolve the issue.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#api#request error#file not found#serialization error#model compatibility

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix [BUG] Dispatch session wedged after April 28 app update; server-side pairing state stuck [2 comments, 3 participants]