You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have searched searched open and closed issues for duplicates
I am submitting a bug report for existing functionality that does not work as intended
This isn't a feature request or a discussion topic
Bug description
i have a signal account connected to two installations: one android install and one desktop install.
i'm in a group with about a dozen people, with some rapid membership changes.
when some members write to this group, their messages show up on both of my installations.
When other members write to this group, their messages only show up on my desktop installation, and do not appear on my android installation.
This means that when i'm looking at android, i sometimes only see one half of a conversation between two members, which is very confusing.
I've dropped from the group and been re-added, in the hopes that this will resolve the problem, but i will report back here if it recurs.
Screenshots
i'm declining to provide screenshots here because the conversations are private. I have saved screenshots of the same chat with both devices
Device
pixel 6a
Android version
15
Signal version
7.25.2
Link to debug log
i'm also declining to post debug logs at the moment because i haven't reviewed the full contexts, but i gathered debug logs from both clients within 24 hours of observing the de-synchronization.
The text was updated successfully, but these errors were encountered:
You have some members blocked, but for some reason that isn't synced across your devices
Your android device has an outdated view of the membership list (the more likely option)
Please let me know if the bug continues after leaving and rejoining, and please share the logs if you can. FWIW we scrub out any PII (there are no phone numbers or accountIds in logs, no message contents, no groupIds, etc).
@greyson-signal thanks for the followup. i haven't seen the problem recurring since leaving and re-joining. Is there a way that i can forward you the logs and accompanying screenshots privately? (the screenshots do show message contents and displaynames which i'd rather not leak. the logs are too big for me to vet myself and there are indeed some potentially correlatable redacted IDs in there. Are there terms or strings i should look for in the logs that would be useful?
Hi there, if you ever need to send us anything outside of github, the recommendation is to send it to support@signal.org and include the github issue number.
However, at this point the logs likely do not contain relevant info anymore (you can rely on logs covering ~2 days). However, if this ever happens again, you could look for the string "Sender is not in the group!" in your log, as this would confirm my second theory. Thanks!
Guidelines
Bug description
i have a signal account connected to two installations: one android install and one desktop install.
i'm in a group with about a dozen people, with some rapid membership changes.
when some members write to this group, their messages show up on both of my installations.
When other members write to this group, their messages only show up on my desktop installation, and do not appear on my android installation.
This means that when i'm looking at android, i sometimes only see one half of a conversation between two members, which is very confusing.
I've dropped from the group and been re-added, in the hopes that this will resolve the problem, but i will report back here if it recurs.
Screenshots
i'm declining to provide screenshots here because the conversations are private. I have saved screenshots of the same chat with both devices
Device
pixel 6a
Android version
15
Signal version
7.25.2
Link to debug log
i'm also declining to post debug logs at the moment because i haven't reviewed the full contexts, but i gathered debug logs from both clients within 24 hours of observing the de-synchronization.
The text was updated successfully, but these errors were encountered: