Skip to content
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

Messages sent via Beeper or Element disappear from Signal Android upon delivery #509

Open
ZaeGitHub opened this issue May 3, 2024 · 5 comments
Labels
bug Something isn't working

Comments

@ZaeGitHub
Copy link

ZaeGitHub commented May 3, 2024

I am not sure if this is an issue with Beeper or the bridge (I don't see how it would be Beeper, but you never know), but when I send messages using this bridge (self-hosted) through Beeper, they show up on Signal Desktop, Android, etc... until they are delivered. Then they, for some reason, disappear entirely from Signal Android. ONLY Signal Android.

How can I troubleshoot this? Are there debug logs I can turn on in the bridge that may explain this?

Steps to Reproduce

  • Self-host this bridge, using Bridge Manager (bbctl) to install it.
  • Authenticate yourself by sending a message to the bridge.
  • Open Signal Android on your phone
  • Send a message to someone else via Beeper mobile or desktop
  • Before delivery, if possible, notice the message being sent.
  • After delivery, notice the message is missing from Signal Android.

Either way, the other user does actually get your message.

@ZaeGitHub ZaeGitHub added the bug Something isn't working label May 3, 2024
@brknkfr
Copy link

brknkfr commented May 12, 2024

I'm experiencing the same on a self-hosted bridge without Beeper. This happens for example, when I send a message over Element (Web, Android, X), so this has to be a bug in the bridge. @ZaeGitHub, you want to change your bug title maybe?

@ZaeGitHub ZaeGitHub changed the title Messages sent via Beeper disappear from Signal Android upon delivery Messages sent via Beeper or Element disappear from Signal Android upon delivery May 12, 2024
@ZaeGitHub
Copy link
Author

Thanks for reporting this on a separate platform @brknkfr. Changed the title to reflect this occurring in Element too, which IMO does lend credence to this being a bridge issue.

@brknkfr
Copy link

brknkfr commented Jun 18, 2024

Still happening with version v0.6.2. As I use the backup function of the Signal app, this is somehow unfortunate ... Will this be fixed with an upcoming release?

@ZaeGitHub
Copy link
Author

+1, I can confirm this is also happening to me. The problem appears to be this bridge in particular, as the Beeper locally-hosted Android bridge works fine.

@neonblind
Copy link

neonblind commented Jun 29, 2024

For me it's exactly the other way around. self-hosted bridge, E2BE enabled, double puppeting manually enabled. message i write with the native signal client wont appear in my own matrix client.

edit: delete-session in matrix/signalbot and relink signal resolved my issue (disappearing messages in matrix when send via native signal) but now i have your problem (disappearing messages in native signal when sending via matrix) as well :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Development

No branches or pull requests

3 participants