Issues with mms and project fi

[GadgetTech]

Hello, I am a long time users of text secure and recently got my invite to project fi from Google. When using it on a nexus 6 I can send mms to certain people and others it simply won't work. Non of them are using the encrypted client and I've tried on WiFi and cellular without a different resault... I've included the URL to the debug file. Thank you in advance.https://gist.github.com/26cb4701cef131177d4e

[rm-you]

I believe I have the same issue. I can't send Pictures in messages, though the most pain is lack of group message support (either Conversation mode, or Broadcast), since it uses MMS. Toggling Wifi Calling support in settings doesn't seem to matter. Google Fi hides all APN settings as well, so I don't know that I can try any solutions that involve APN tweaks. Very frustrating. :(

[GadgetTech]

Interesting, that's probably the reason, if they cant get the APN settings from them its hard to make everything work. It is because I'm back to using hangouts... I hope we can get some traction on this at some point.

[rm-you]

Might be a duplicate of #4131 (or rather, looks like that one came later but just happens to be more specific).

Try switching manually to T-Mobile (can use Fi Spy or find the dialer code online somewhere). I am able to send on TMO but not Sprint, per that issue. I wonder if your problem is the same? Then we could consolidate this.

[rm-you]

Looking at your log it seems this is the same issue -- getting the Authentication Required response from the MMS server with Sprint. Try when you are forced onto T-Mobile and I bet it will work.

[Tweakyth13f]

Having this exact issue. When on Sprint LTE, I cannot send a photo via even the updated Signal App (even with the wifi compatibility toggled). Using Fi Spy to force myself to Tmobile, it worked without issue. I'm on a 16GB Nexus 5X.

Debug log: https://gist.github.com/anonymous/10ada2e25e912bd98079

Second Set: https://gist.github.com/anonymous/992f6711d04e0ffd4620

[peteraldous]

I did some digging in my debug logs. Like most of you, I determined that the problem arises when I'm on Sprint's network but that I can send MMS just fine when on T-Mobile's network.

I spent a little while on email and on the phone with Project Fi and Google support. The answer I got was that the app is "not supported" on Sprint's network. It's impossible for me to tell if that means that Signal needs to be tested more extensively on Sprint's network or if Sprint is failing to support the protocol properly (which could be worked around) or if Sprint is actively suppressing traffic from some applications.

[matthewdavis]

Issue 4131 is related to this and seems to have more relevant info.

#4131

[evantd]

#4131 has been resolved and more changes were made in May 2017 that may have resolved this issue. Is it still a problem for you?

[peteraldous]

I lurked on #4131 for a while and a fix came through the Play Store not long after it wrapped up that fixed things. The problem was always intermittent, so it's hard to say; I haven't sent many insecure MMS since the latest changes to CompatMmsConnection.java (May 24 2017) but I have sent a few and they've all worked. So although one can never be certain about the absence of an intermittent problem, I'd say we're good to go.

[automated-signal]

GitHub Issue Cleanup:
See #7598 for more information.