Repository navigation
Android: agent replies not visible in DM, and presence stuck showing agent offline #2971
Description
Related to #2970 (same Android session), but these are separate symptoms worth their own report.
1. Incoming messages not displayed
In a DM with an agent, the agent's replies did not appear on Android at all. The user had to switch to Desktop to see them. The same DM on Desktop showed the full exchange, so the events were on the relay and the agent had published normally — Android simply did not render them.
The messages were sent while the user was actively in that DM on the phone, so this is not a stale-cache-on-open case.
2. Presence shows the agent as offline
Android showed the agent as offline in the same DM. The relay reported it online:
$ buzz users presence --pubkeys a1defd95...7bcc
[{"pubkey":"a1defd95...7bcc","status":"online","updated_at":1785069022}]
So the presence indicator on Android does not reflect current relay state.
Impact
Combined with #2970, Android is currently unreliable for agent conversations in both directions: mentions can fail to attach outbound, and replies can fail to appear inbound. From the user's side the agent looks broken or unresponsive when it is working correctly.
Environment
Buzz Android app. Desktop does not reproduce either symptom.
Activity
Dirtywater97 commentedon Jul 26, 2026
Additional data point: this is a regression, not longstanding behavior.
The same user, same device, same DM worked correctly the previous evening (2026-07-25). All three symptoms — dropped mention tags (#2970), replies not rendering, and stale presence — appeared together on 2026-07-26 with no change on the user's side.
Since all three landed at once, a single cause is plausible: an app update, or a change to how the client subscribes to / filters relay events. Worth checking what shipped between those dates.
Dirtywater97 commentedon Jul 26, 2026
Update after clearing app data / cache on Android.
Clearing helped partially: thread replies now appear in the channel list with the sender's avatar. But opening a thread shows "0 messages" and an empty view, even though the thread has many replies (confirmed present on Desktop and via
buzz messages thread).So the current Android state is:
That makes any threaded conversation unreadable on Android. Given this platform routes agent replies into threads by default, it means agent conversations cannot be followed on mobile at all.
Cache clearing being a partial fix suggests the local store and the relay subscription disagree — the thread view may be reading only from local state rather than fetching thread events from the relay.
Dirtywater97 commentedon Jul 26, 2026
Confirmed isolation of the rendering bug on Android:
So the Android renderer is fine for the main channel scroll; the thread detail view is the single broken surface. Everything else reported here follows from that.
Workaround in use: the agent now replies top-level instead of threading, which restores mobile readability at the cost of thread structure.
daguiler76 commentedon Jul 31, 2026
Independent iOS reproduction of the presence half of this report in a self-hosted 1:1 DM:
status: onlinewith a freshupdated_atvalue.The same session also reproduced missing live threaded replies, now tracked with a more specific storage-layer cause in #3293. Top-level agent messages displayed on iOS, while ordinary thread replies did not. The stale offline badge therefore remains a separate mobile presence synchronization/rendering defect, and this data point confirms it is not Android-only.