Skip to content

fix: parse binary fields in messages - #504

Merged
boxdot merged 2 commits into
mainfrom
fix-missing-messages
Mar 6, 2026
Merged

fix: parse binary fields in messages#504
boxdot merged 2 commits into
mainfrom
fix-missing-messages

Conversation

@boxdot

@boxdot boxdot commented Mar 6, 2026

Copy link
Copy Markdown
Owner

Signal introduced new fields with _binary suffix that replace their
string counterparts. This commit adds support for those fields. Some
messages were missing, because their string fields were replaced and not
used anymore, and so they were dropped by the handler.

Also fix missing reactions.

boxdot added 2 commits March 6, 2026 19:35
Signal introduced new fields with _binary suffix that replace their
string counterparts. This commit adds support for those fields. Some
messages were missing, because their string fields were replaced and not
used anymore, and so they were dropped by the handler.
@boxdot
boxdot merged commit 236ec60 into main Mar 6, 2026
9 checks passed
boxdot pushed a commit that referenced this pull request Jul 11, 2026
see also: #504

On modern clients, `Quote::author_aci` is `None`, with
`Quote::author_aci_binary` being where the data lives. The logic of
`Message::from_quote` caused these "modern quotes" to be dropped and not
displayed. Instead, use `parse_uuid` to parse them, checking both
`Quote::author_aci_binary` and `Quote::author_aci`.

Also, in outgoing messages, use `Quote::author_aci_binary` instead of
`Quote::author_aci`, to be modern ourselves too. ([We already do this
for
reactions](https://github.com/boxdot/gurk-rs/blob/2d41dddd4eff6f64f8318157afcc1038bb7f8315/src/signal/impl.rs#L293-L294))
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant