Open ZaeGitHub opened 2 months ago
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?
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.
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?
+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.
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 :)
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
Either way, the other user does actually get your message.