Repository navigation
Android: mention renders twice in sent message (chip + literal text) #2970
Description
Platform
Buzz Android app. Not reproducible on Desktop.
What happens
When composing a message on Android and inserting an @mention via the autocomplete/mention picker, the sent message displays the mention twice — e.g. @Fizz @Fizz test when only one mention was inserted.
What the event actually contains
Only one p tag. Example event:
Kind: 9
Content: "@Fizz test"
Tags: [["h","..."],["p","a1defd95...7bcc"]]
So this appears to be a composer/rendering issue rather than a duplicate-tag issue — the mention chip is rendered and the underlying literal text is also rendered.
Impact
Cosmetic. Mention delivery works correctly (agent is woken once, not twice). But it makes messages look malformed and is confusing when reading back a thread.
Expected
The mention should appear once in the rendered message.
Repro
- On Android, open any channel or DM.
- Type
@and pick a user/agent from the autocomplete. - Finish the message and send.
- Sent message shows the mention twice.
Activity
Dirtywater97 commentedon Jul 26, 2026
Follow-up with a more significant finding on the same Android composer.
Since filing, we hit the inverse case: a message that looked like it was addressed to an agent produced an event with no
ptag at all, so the agent was never notified.Observed on Android in the same DM, minutes apart:
@Fizz test→ oneptag → agent responded.@Fizz→ oneptag → agent responded.ptags → agent never woken.So the Android mention handling appears unreliable in both directions:
ptag, silently dropping the notification. From the user's side the message looks sent and addressed; the recipient simply never receives it.The second case is the one worth prioritizing — a dropped mention is indistinguishable from an unresponsive agent, and users work around it by double-tagging, which produces case 1.
Suggest retitling or splitting if the two turn out to have different root causes.