-
-
Notifications
You must be signed in to change notification settings - Fork 75
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Replies to replies have "null" attachment, causing broken display on desktop Signal app #238
Comments
I can't reproduce this with latest mautrix-signal |
@Mikrz what client are you using? I am having the same thing from ement, but not from element. |
Sorry @htayj , this issue is from 2 years ago, and I've since stopped bridging Signal. The bug only appeared in the Signal app for me, and the only other app I used to connect to the matrix server was Element. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I am using the most recent build of the bridge via github on commit c4f7c97 though this issue has been happening for a while.
When replying to another message that includes a reply, an invalid attachment is created and causes a null attachment icon to show on desktop Signal:
Grey bubble was sent from Signal's Android app, blue was sent via the bridge. the "2345" message was sent with line 382 shown below removed, "back atcha" was sent with that line present.
I've confirmed this issue stems from this section:
signal/mautrix_signal/portal.py
Lines 375 to 382 in 7227540
Apparently desktop Signal does not handle this odd behaviour as gracefully as Android and iOS. I would assume the fix would be to add the ability for the bridge to determine if the reply has an attachment or not per the TODO, though I'm unsure I'd be able to implement the fix in a quick manner so I'll leave this issue for now.
Additionally, based on the commit (498e0f2) that added that line to begin with, it was a quick fix for iOS to render replies properly so I would be unable to test any changes I make due to lack of an iPhone.
The text was updated successfully, but these errors were encountered: