Bridge replies don't show as replies from Status to Discord #16323
Assignees
Labels
Milestone
Comments
jrainville
added
bug
jrainville
added a commit
to status-im/matterbridge
that referenced
this issue
Sep 12, 2024
Needed for status-im/status-desktop#16323 There were multiple problems. 1. The ParentID was not set correctly when a message was sent from Status 2. We didn't send back the ID of messages that we sent, so the gateway couldn't associate the new messages to the old ones 3. Missing param in the toml config `PreserveThreading` 4. Discord messages are weirdly formatted when a reply is send. It cannot use webhooks, so we need to pass the username directly in the message (it's ugly, but it works) Finally, there was an issue on the status-go side. We tried to use the discord message ID to find the replies, but the bridge already converts it to the right ID, so we could just use it directly
jrainville
added a commit
to status-im/status-go
that referenced
this issue
Sep 12, 2024
Fixes status-im/status-desktop#16323 The problem was that the code expected to receive the Discord message ID, but the bridge is smart enough to return the Status message ID already, so there is no need to try and convert it. There were also a couple issues in the bridge code itself.
jrainville
added a commit
to status-im/status-go
that referenced
this issue
Sep 12, 2024
Fixes status-im/status-desktop#16323 The problem was that the code expected to receive the Discord message ID, but the bridge is smart enough to return the Status message ID already, so there is no need to try and convert it. There were also a couple issues in the bridge code itself.
jrainville
added a commit
to status-im/status-go
that referenced
this issue
Sep 12, 2024
Fixes status-im/status-desktop#16323 The problem was that the code expected to receive the Discord message ID, but the bridge is smart enough to return the Status message ID already, so there is no need to try and convert it. There were also a couple issues in the bridge code itself.
jrainville
added a commit
to status-im/status-go
that referenced
this issue
Sep 13, 2024
Fixes status-im/status-desktop#16323 The problem was that the code expected to receive the Discord message ID, but the bridge is smart enough to return the Status message ID already, so there is no need to try and convert it. There were also a couple issues in the bridge code itself.
siddarthkay
pushed a commit
to status-im/matterbridge
that referenced
this issue
Sep 14, 2024
Needed for status-im/status-desktop#16323 There were multiple problems. 1. The ParentID was not set correctly when a message was sent from Status 2. We didn't send back the ID of messages that we sent, so the gateway couldn't associate the new messages to the old ones 3. Missing param in the toml config `PreserveThreading` 4. Discord messages are weirdly formatted when a reply is send. It cannot use webhooks, so we need to pass the username directly in the message (it's ugly, but it works) Finally, there was an issue on the status-go side. We tried to use the discord message ID to find the replies, but the bridge already converts it to the right ID, so we could just use it directly
jrainville
added a commit
to status-im/status-go
that referenced
this issue
Sep 23, 2024
Fixes status-im/status-desktop#16323 The problem was that the code expected to receive the Discord message ID, but the bridge is smart enough to return the Status message ID already, so there is no need to try and convert it. There were also a couple issues in the bridge code itself.
jrainville
added a commit
to status-im/status-go
that referenced
this issue
Sep 24, 2024
Fixes status-im/status-desktop#16323 The problem was that the code expected to receive the Discord message ID, but the bridge is smart enough to return the Status message ID already, so there is no need to try and convert it. There were also a couple issues in the bridge code itself.
jrainville
added a commit
to status-im/status-go
that referenced
this issue
Sep 27, 2024
Fixes status-im/status-desktop#16323 The problem was that the code expected to receive the Discord message ID, but the bridge is smart enough to return the Status message ID already, so there is no need to try and convert it. There were also a couple issues in the bridge code itself.
github-project-automation
bot
moved this from Code Review
to Done
in Status Desktop/Mobile Board
github-project-automation
bot
moved this from Code Review
to Done
in Status Desktop/Mobile Board
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug Report
Description
When you do a reply on Status, the message on Discord doesn't show as a reply, just like a normal message.
When sending a reply from Discord however, it works fine.
Steps to reproduce
Expected behavior
The message shows a a reply on both platforms
Actual behavior
The message shows as a reply only on Status. It shows as a normal message on Discord
Additional Information
The text was updated successfully, but these errors were encountered: