[Bug] Mesh: messaging a federation contact fails with 'Missing contact_id' #39
Loading…
x
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Sending a mesh message to a federation-only contact (e.g. 'Arch Dev') failed with 'Missing contact_id', especially on radio-less nodes.
Root cause: the UI gave federation-only rows a NEGATIVE placeholder contact_id (derived from a DID hash), but the backend parses contact_id as u64, so a negative value deserialized to None. The negative id also never matched the positive federation-synthetic id that federation-routed messages are stored under, so those threads looked empty.
Fixed in commit
1ea3f8d6:Pending live deploy verification.