When I create a MMS group through signal, replies from other members create a new thread. The original group does not list me as a member, but the new group does.
(defauly sms app, wifi calling compatibility mode off, project fi network)
Actual result: the reply creates a new thread/group
Expected result: replies go to the same thread/group
First group


After replies:


Device: Pixel
Android version: 8.1.0
Signal version: 4.18.3
https://debuglogs.org/cfed3ebb12a7ba60f98ccce30677996f5fc46c55b899e1e4d9a92638a4d9cbfe
This is a re-submission of https://github.com/signalapp/Signal-Android/issues/7161 which was closed during the cleanup (https://github.com/signalapp/Signal-Android/issues/7598)
Happens to me always. I'm on Sprint
Happens to me as well, Project Fi. And if you try to be clever and add yourself to the original group when creating it, it says you're already a member.
Just happened today: https://debuglogs.org/4774c97924b4246cd72cfce370e6ab1f303d8b6693385be9deaf109473f92ff5
The original group lists my name first while the new group lists my name last
Same issue, TMobile.
Same issue, Project Fi.
Please don't comment "same issue". It's well-established now that this is a bug. What this issue needs now is not more people confirming it, but for someone to actually fix it.
Looks like the issue is around https://github.com/signalapp/Signal-Android/blob/d9ba6962c792033ea99f8e24fb4482ac1020f8bd/src/org/thoughtcrime/securesms/groups/GroupManager.java#L51
The code appears to add the current local user to the new group, but it obviously doesn't.
It seems like it's adding the local user. If I create a new group but attempt to add myself as well it tells me "you are already in the group".
I have observed a similar issue on my dual SIM phone. In one-on-one conversations using my non-Signal SIM I can successfully send MMS images and they end up in the correct conversation, but when I receive MMS images from the other person Signal creates a new group with the other person, my non-Signal number any my Signal number.
I think this could be regarded as the same issue since in both cases incoming MMS messages are not attributed to the correct conversation. Looking at the pull request #8296 I鈥檓 not sure though that this solution also works with dual SIM phones and with one-on-one conversations. It would be great if the original issue and mine could be solved in one go, so if someone more familiar with the Signal code could check this, that would be cool! Otherwise I might try finding some time to figure out the problem with my dual SIM MMS messages and come up with a separate issue or pull request.
Most helpful comment
Please don't comment "same issue". It's well-established now that this is a bug. What this issue needs now is not more people confirming it, but for someone to actually fix it.