Skip to content

Android App v2026.5.25 node mode chat.send never reaches Gateway v2026.6.5 #91872

Closed

Description

@1422671081-hub

Android App v2026.5.25 node mode chat.send never reaches Gateway v2026.6.5

Environment

  • Gateway: 2026.6.5 (5181e4f)
  • Android App: 2026.5.25
  • Device: Xiaomi 17 Ultra
  • Network: Tailscale wss://
  • Pairing: Setup Code + autoApproveCidrs

Symptoms

  1. Pairing succeeds, device shows node + operator roles
  2. Chat panel can pull history (chat.history OK)
  3. WebChat replies are pushed to phone correctly (WebSocket push OK)
  4. When tapping send on phone: input clears, message appears in chat, no error shown
  5. BUT chat.send never appears in Gateway logs

Verification (Gateway side)

openclaw devices list shows correct scopes:
Xiaomi 17 Ultra | Roles: node, operator | Scopes: operator.read, operator.write, operator.approvals, talk.secrets

Gateway logs - operator connection reads history correctly:
14:46:29 res OK chat.history 548ms conn=9f479141
14:46:31 res OK chat.history 184ms conn=9f479141

WebChat sends work normally (for comparison):
res OK chat.send runId=... conn=f6a68007

chat.send from Android never logged after tapping send.

References

Analysis

chat.send is missing only in the phone-to-gateway direction. The operator connection works for reading history and receiving push. Appears to be a client-side issue where the Android app's send button does not actually fire chat.send over the operator WebSocket, or is intercepted by local session state before sending. Consistent with SendButton/healthOk/pendingRunCount analysis from community.

Activity

  1. clawsweeper commented on Jun 10, 2026

    @clawsweeper
    Contributor

    Codex review: keeping this open for maintainer follow-up; there is still a little grit to resolve. Reviewed June 21, 2026, 4:43 PM ET / 20:43 UTC.

    Summary
    Keep open. Current main and v2026.6.9 still show Android chat send wiring and status-blind optimistic UI handling, but neither source nor the open related PRs proves the reported phone-to-Gateway chat.send frame loss is fixed.

    Reproducibility: no. The reporter supplied concrete Gateway-side logs and current source shows the Android UI routes to chat.send, but this review did not reproduce the Android/Tailscale/Gateway missing-frame path on current main.

    Ways to help us reproduce this

    • Add a screenshot or short recording showing the behavior.
    • Add expected vs actual behavior.

    Next step
    The issue already has no-new-fix-pr, needs-maintainer-review, and needs-info labels, and the missing-frame symptom needs live Android proof before an automated repair can choose the correct code path.

    Review details

    Best possible solution:

    Run a maintainer-owned Android live reproduction against current Gateway with Android logs and Gateway request logs; if the frame is still absent, fix the Android outbound RPC/session layer or compose it with the ACK/composer work already open.

    Do we have a high-confidence way to reproduce the issue?

    No. The reporter supplied concrete Gateway-side logs and current source shows the Android UI routes to chat.send, but this review did not reproduce the Android/Tailscale/Gateway missing-frame path on current main.

    Is this the best way to solve the issue?

    Not yet. The best fix cannot be chosen until live proof distinguishes a pre-send Android gate, WebSocket transport failure, Gateway auth/scope rejection, or terminal ACK/status handling issue.

    AGENTS.md: found and applied where relevant.

    Remaining risk / open question:

    • No real Android/Tailscale/Gateway reproduction was run in this read-only review, so the reported missing phone-origin chat.send frame remains unverified on current main.
    • The open terminal-ACK PR may fix adjacent stuck or failed send state, but its current evidence does not prove a phone-origin request frame that never appears in Gateway logs is fixed.
    • The older similar Android send-button issue was closed against then-current source, but this newer report uses later Gateway/App versions and says the same missing-frame symptom persists.

    Codex review notes: model internal, reasoning high; reviewed against 2609b9722280.

    Label changes

    Label justifications:

    • P1: The report describes a user-facing Android chat workflow where outbound messages appear locally but are not delivered to Gateway.
    • impact:message-loss: The central symptom is a phone-originated chat message being lost before Gateway receives or logs chat.send.
    Evidence reviewed

    Acceptance criteria:

    • Install a current Android build or latest released APK, connect over the reported WSS/Tailscale-style path to a current Gateway, pair with node and operator scopes, tap Android Chat send, and capture Android logcat plus Gateway request logs for the matching chat.send request.
    • If reproduced, add focused Android coverage around ChatController/GatewaySession or the affected composer surface, then validate with the relevant Android JVM tests and a real Android-to-Gateway proof run.

    What I checked:

    • Repository policy read: Read the full root AGENTS.md, scoped Gateway AGENTS files, and VISION.md; no apps/android scoped AGENTS.md exists, so root Android/Gateway review policy applies. (AGENTS.md:1, 2609b9722280)
    • Live issue context: The live issue reports Android v2026.5.25 with Gateway v2026.6.5, successful pairing/history/push, and no Gateway log entry for Android-originated chat.send; current labels still request maintainer review and more info.
    • Android send path on current main: Android ChatController still adds optimistic local state, builds chat.send params, calls session.request("chat.send", ...), then treats a runId-like response as accepted without checking terminal ACK status. (apps/android/app/src/main/java/ai/openclaw/app/chat/ChatController.kt:246, 2609b9722280)
    • Android composer clears before acceptance: The full Android ChatScreen clears input and attachments before launching the send coroutine, so visible local UI success does not prove Gateway accepted or received the frame. (apps/android/app/src/main/java/ai/openclaw/app/ui/chat/ChatScreen.kt:221, 2609b9722280)
    • GatewaySession request frame path: GatewaySession.request parses params and Connection.request builds a req frame and sends it via OkHttp WebSocket; a socket send failure throws locally, so a live trace is needed to distinguish pre-send gating from transport or Gateway receipt. (apps/android/app/src/main/java/ai/openclaw/app/gateway/GatewaySession.kt:360, 2609b9722280)
    • Gateway method contract: chat.send is an operator.write Gateway method, and the Android docs describe Android Chat send as chat.send, matching the reporter's expected contract. (src/gateway/methods/core-descriptors.ts:211, 2609b9722280)

    Likely related people:

    • obviyus: Shortlog and git history show Ayaan Zaidi as the heaviest contributor across the Android ChatController, chat UI, GatewaySession, and NodeRuntime files, including assistant auto-send and explicit setup auth work adjacent to this behavior. (role: Android chat/history contributor; confidence: high; commits: 34a5c47351d1, 186647cb749b, fa150f882834; files: apps/android/app/src/main/java/ai/openclaw/app/chat/ChatController.kt, apps/android/app/src/main/java/ai/openclaw/app/ui/chat/ChatSheetContent.kt, apps/android/app/src/main/java/ai/openclaw/app/gateway/GatewaySession.kt)
    • vincentkoc: Current blame for the active Android chat send, composer, GatewaySession, and NodeRuntime lines points to Vincent Koc's recent snapshot/release commits in this shallow checkout. (role: recent current-main area contributor; confidence: medium; commits: c2ee9b0be8ae, c645ec4555c0; files: apps/android/app/src/main/java/ai/openclaw/app/chat/ChatController.kt, apps/android/app/src/main/java/ai/openclaw/app/ui/chat/ChatScreen.kt, apps/android/app/src/main/java/ai/openclaw/app/ui/chat/ChatSheetContent.kt)
    • steipete: History shows Peter Steinberger authored adjacent Android operator bootstrap reconnect and stored-auth work that can affect whether the operator session used for chat sends is connected and authorized. (role: Android gateway/session auth contributor; confidence: medium; commits: c3a2701c45b1; files: apps/android/app/src/main/java/ai/openclaw/app/gateway/GatewaySession.kt, apps/android/app/src/main/java/ai/openclaw/app/NodeRuntime.kt)
    • lixuankai: Shortlog and prior issue history connect lixuankai to Android session-key/default behavior, which determines which Gateway chat session Android targets. (role: adjacent session-default behavior contributor; confidence: low; commits: f0a57fad42e1; files: apps/android/app/src/main/java/ai/openclaw/app/chat/ChatController.kt, apps/android/app/src/main/java/ai/openclaw/app/NodeRuntime.kt)
    How this review workflow works
    • ClawSweeper keeps one durable marker-backed review comment per issue or PR.
    • Re-runs edit this comment so the latest verdict, findings, and automation markers stay together instead of adding duplicate bot comments.
    • A fresh review can be triggered by eligible @clawsweeper re-review comments, exact-item GitHub events, scheduled/background review runs, or manual workflow dispatch.
    • PR/issue authors and users with repository write access can comment @clawsweeper re-review or @clawsweeper re-run on an open PR or issue to request a fresh review only.
    • Maintainers can also comment @clawsweeper review to request a fresh review only.
    • Fresh-review commands do not start repair, autofix, rebase, CI repair, or automerge.
    • Maintainer-only repair and merge flows require explicit commands such as @clawsweeper autofix, @clawsweeper automerge, @clawsweeper fix ci, or @clawsweeper address review.
    • Maintainers can comment @clawsweeper explain to ask for more context, or @clawsweeper stop to stop active automation.
  2. added
    P1High-priority user-facing bug, regression, or broken workflow.
    impact:message-lossChannel message delivery can be lost, duplicated, or misrouted.
    issue-rating: 🦐 gold shrimpDecent issue quality, but reproduction details are still incomplete.
    clawsweeper:needs-infoClawSweeper needs more reporter information before it can verify this issue.
    clawsweeper:no-new-fix-prClawSweeper does not recommend queueing a new automated fix PR for this issue.
    clawsweeper:needs-maintainer-reviewClawSweeper marked this issue as needing maintainer review before automation.
    issue-rating: 🦪 silver shellfishThin issue quality; more reproduction proof or environment detail is needed.
    issue-rating: 🐚 platinum hermitGood issue quality with a plausible reproduction path needing some confirmation.
    clawsweeper:needs-live-reproClawSweeper needs live local, crabbox, or manual validation to confirm this issue.
    clawsweeper:fix-shape-clearClawSweeper found a clear likely implementation shape for this issue.
    and removed
    issue-rating: 🦐 gold shrimpDecent issue quality, but reproduction details are still incomplete.
    clawsweeper:needs-infoClawSweeper needs more reporter information before it can verify this issue.
    issue-rating: 🦪 silver shellfishThin issue quality; more reproduction proof or environment detail is needed.
    clawsweeper:needs-live-reproClawSweeper needs live local, crabbox, or manual validation to confirm this issue.
    issue-rating: 🐚 platinum hermitGood issue quality with a plausible reproduction path needing some confirmation.
    clawsweeper:fix-shape-clearClawSweeper found a clear likely implementation shape for this issue.
    on Jun 10, 2026
  3. elisspace commented on Jun 30, 2026

    @elisspace

    I’m seeing the same symptom on a newer setup.

    Gateway: OpenClaw 2026.6.10 (aa69b12)

    Android app/node reports: 2026.6.9

    Device: Pixel 9 Pro, approved/connected, roles node + operator

    Operator scopes: operator.approvals, operator.read, operator.talk.secrets, operator.write

    Android Main chat can display history. A server-side diagnostic assistant reply written into the same mobile session appeared in the Android app after refresh, so chat.history / display works.

    But when sending from Android, the user message is appended to the session transcript and no assistant response starts. During send attempts, gateway logs show no chat.send, no sessions.send, and no agent run. Session token usage does not change. One captured Android send appended a user row at 2026-06-30T15:08:56Z with no matching chat.send or agent run around that time.

    The phone lacks operator.pairing, so device.pair.list logs missing scope: operator.pairing, but chat.history requires operator.read and chat.send requires operator.write, both present. This seems consistent with the Android client persisting/syncing the user row without invoking chat.send, rather than a gateway/model/auth problem.

  4. secondfoxgit commented on Jul 2, 2026

    @secondfoxgit

    I can reproduce the same issue on a newer setup.

    Environment

    • Gateway: OpenClaw 2026.6.11
    • Android app: 2026.6.9 / build 2026060901
    • Device: Google Pixel 8 Pro
    • Network: Tailscale / secure wss:// gateway endpoint
    • Pairing: setup-code pairing, device has both node + operator roles
    • Node state: paired, connected, approved

    Observed behavior

    The Android app connects successfully and can display chat history. Android node transport also works: gateway-side device.status and device.info calls to the phone succeed.

    However, sending from the Android Chat tab does not start an assistant run:

    • The Android-origin user message is persisted into the selected session transcript.
    • Gateway logs show normal UI/operator activity such as sessions.list and chat.history.
    • Gateway logs show no chat.send for the Android-origin send attempt.
    • No assistant row is created and no model run starts.

    I tested both the default Main lane and another selected session lane. In both cases the user message was stored, but no chat.send reached the gateway.

    This does not look like a gateway reachability, model/provider, Tailscale, or node approval issue. It looks like the Android Chat client stores/syncs the user message without invoking chat.send.

  5. self-assigned this
    on Jul 2, 2026
  6. steipete commented on Jul 2, 2026

    @steipete
    Contributor

    Maintainer live proof: closing this as fixed by #91049 / 3ff0c29f9d09cbcbadc7b2c6855bb73bb94364c0, included in v2026.6.11.

    I reproduced the reported matrix on a clean Android 16 emulator: Android APK v2026.6.9 -> Tailscale Serve wss:// -> Gateway v2026.6.5. The uniquely marked Android send was written to the isolated Gateway session transcript. I then deliberately removed downstream provider auth: the v2026.6.9 client showed the reported silent user row, while the same send from the v2026.6.11 Android tree displayed the exact Gateway agent failure. Finally, current Android -> current Gateway over the same WSS path completed a real model turn and rendered the reply.

    The missing chat.send console line was a misleading signal, not evidence that the frame was absent. Normal Gateway WebSocket logging records incoming request timing but, outside verbose mode, only prints failed or slow responses; a fast accepted chat.send can therefore produce no method line. The persisted user transcript row is stronger evidence: Android sends through ChatController -> GatewaySession.request("chat.send"), and the Gateway chat.send handler owns that transcript write.

    #91049 fixed the actual user-visible failure mode after the v2026.6.9 APK: terminal send failures and failed agent starts no longer look like a successful silent send. The fix shipped in the v2026.6.11 tag. If this still reproduces from an Android build containing that commit, please open a fresh issue with Android logcat plus the correlated Gateway diagnostic/lifecycle error; absence of a normal chat.send console line alone is not a failed-ingress signal.

    Proof references:

  7. elisspace commented on Jul 8, 2026

    @elisspace

    I am seeing what looks like the same failure mode on newer versions, with one extra detail that may help narrow it down.

    Environment

    • Gateway/OpenClaw: 2026.6.11 (e085fa1)
    • Android app/node UI: v2026.6.11
    • Device: Pixel 9 Pro
    • Route: public WSS via wss://gateway.REDACTED.com
    • Pairing flow: QR/setup code, then manual node approval
    • Node status after approval: paired · connected · approved
    • Device roles/scopes:
    • roles: node, operator
    • operator scopes: operator.approvals, operator.read, operator.talk.secrets, operator.write

    Symptoms

    This matches the original report very closely:

    1. Android pairs successfully.
    2. Node shows as connected and approved.
    3. Android Main/chat can read session history.
    4. Assistant replies written from elsewhere show up on the phone.
    5. Tapping send in Android Main clears the input and the message appears in the chat.
    6. No assistant response is produced.
    7. Gateway logs show Android polling/status/history activity, but no chat.send request from Android for the sent message.

    Additional detail from this repro

    In this repro, the Android-originated user message is not only visible locally on the phone: it is also written into the server-side session transcript JSONL.

    Example transcript entry after sending test dispatch 2039 from Android Main:

    {
    "type": "message",
    "timestamp": "2026-07-08T20:42:41.926Z",
    "message": {
    "role": "user",
    "content": "test dispatch 2039",
    "timestamp": 1783543361743,
    "idempotencyKey": "9fb163e9-e1eb-454c-9ada-f961a6a52f7:user"
    }
    }

    But no agent run starts afterward. The session age updates, and the user turn is present in the transcript, but dispatch does not happen.

    That suggests this may not be only a local optimistic UI issue. The user turn is reaching some persistence/projection path, but it appears to bypass the normal chat.send path that starts the agent turn.

    Gateway log evidence

    Around the Android send attempt, the gateway logs show normal Android connection activity such as:

    res OK sessions.list
    res OK node.list
    res OK channels.status
    res OK chat.history
    res ERR device.pair.list missing scope: operator.pairing
    

    But there is no corresponding:

    res OK chat.send ...
    

    for the Android-originated message.

    The missing operator.pairing error appears unrelated to the chat failure. The Android bootstrap/operator token intentionally excludes operator.pairing, and the phone is otherwise connected, approved, able to read history, and able to receive displayed replies.

    Manual dispatch comparison

    If I manually run an agent turn against the same node session from the gateway CLI, the assistant response is written to the same session and appears on the phone correctly.

    That confirms:

    • Android can display assistant messages.
    • The session is valid.
    • The node is connected.
    • The issue is specifically that Android Main send does not launch the agent turn.

    Expected behavior

    When Android Main sends a chat message, the gateway should receive/log chat.send, start an agent run, and stream or deliver the assistant reply back to the same session.

    Actual behavior

    The Android-originated user message is appended to the session transcript, but no chat.send appears in gateway logs and no agent run starts.

    Why I think this is the same issue

    The core symptoms match this issue exactly:

    • Android node mode
    • pairing succeeds
    • history works
    • replies from elsewhere show on phone
    • send appears locally successful
    • no chat.send logged
    • no assistant run

    The main difference is that this is on 2026.6.11, not 2026.5.25 / 2026.6.5, and the transcript append providesa slightly more specific failure shape: the user message is reaching persistent session state, but not the agent dispatch path.

  8. locked as resolved and limited conversation to collaborators on Aug 8, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

P1High-priority user-facing bug, regression, or broken workflow.clawsweeper:needs-infoClawSweeper needs more reporter information before it can verify this issue.clawsweeper:needs-maintainer-reviewClawSweeper marked this issue as needing maintainer review before automation.clawsweeper:no-new-fix-prClawSweeper does not recommend queueing a new automated fix PR for this issue.impact:message-lossChannel message delivery can be lost, duplicated, or misrouted.issue-rating: 🦐 gold shrimpDecent issue quality, but reproduction details are still incomplete.

Type

No type

Fields

Priority

None yet

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions