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

New MMS group created for responses to a group created through signal #7683

Closed
4 tasks done
benmayne opened this issue Apr 15, 2018 · 12 comments
Closed
4 tasks done

New MMS group created for responses to a group created through signal #7683

benmayne opened this issue Apr 15, 2018 · 12 comments

Comments

@benmayne
Copy link


Bug description

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)

Steps to reproduce

  • create a mms group
  • send a message
  • wait for someone to reply

Actual result: the reply creates a new thread/group
Expected result: replies go to the same thread/group

Screenshots

First group
2018-04-15 09 33 50
2018-04-15 09 56 12

After replies:
2018-04-15 09 33 41
2018-04-15 09 33 45

Device info

Device: Pixel
Android version: 8.1.0
Signal version: 4.18.3

Link to debug log

https://debuglogs.org/cfed3ebb12a7ba60f98ccce30677996f5fc46c55b899e1e4d9a92638a4d9cbfe

This is a re-submission of #7161 which was closed during the cleanup (#7598)

@dcherian
Copy link

Happens to me always. I'm on Sprint

@2-4601 2-4601 added the mms label Apr 16, 2018
@hunleyd
Copy link

hunleyd commented Apr 20, 2018

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.

@dcherian
Copy link

dcherian commented May 2, 2018

Just happened today: https://debuglogs.org/4774c97924b4246cd72cfce370e6ab1f303d8b6693385be9deaf109473f92ff5

The original group lists my name first while the new group lists my name last

@shanep2300
Copy link

Same issue, TMobile.

@ghost
Copy link

ghost commented Jun 3, 2018

Same issue, Project Fi.

@strugee
Copy link

strugee commented Jun 3, 2018

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.

@wesinator
Copy link

Looks like the issue is around

memberAddresses.add(Address.fromSerialized(TextSecurePreferences.getLocalNumber(context)));

The code appears to add the current local user to the new group, but it obviously doesn't.

@slicknic
Copy link

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".

@mfsch
Copy link

mfsch commented Oct 26, 2018

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’m 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.

ksander314 pushed a commit to ksander314/Signal-Android that referenced this issue Apr 12, 2019
@fleapower
Copy link

fleapower commented Apr 21, 2021

This issue is two years old, and other threads state it had been fixed. However, it is persisting on my Samsung A51 on T-Mobile. Is it being tracked in another thread? Thanks!

@strugee
Copy link

strugee commented Apr 22, 2021

@fleapower you are likely encountering a different bug. Please report a new issue, and make sure to follow the proper procedure - in particular, please search to see if the bug you're encountering has already been reported.

@benmayne
Copy link
Author

benmayne commented May 2, 2021

Looks like there's an open version of it already here: #9213

(I'm about to add new logs to that one since it's back for me as well)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging a pull request may close this issue.

10 participants