I have:
Sending pictures to AT&T users via MMS results in the recipient receiving the following message instead of the picture:
One or more of the message components have been deleted by MMS Adaptation. Either the message was too large or the components were unsuitable for your handset.
I have encountered this problem when:
An AT&T employee said in 2015 that their MMS size limit was 1MB but I have had this problem occur when sending images smaller than that.
I am not sure if this issue is reproducible 100% of the time.
This error message has also been mentioned in issues #380 #494 #511 #920 #1204
Actual result: The recipient receives an error message
Expected result: The recipient should receive the picture
Device: Nexus 5X
Android version: 7.0 (N5D91L)
Signal version: 3.24.1
SMS delivery reports: On
'WiFi Calling' compatibility mode: Off
I'm having the same issue. Signal installed on a Nexus 5x and Nexus 6P (project fi). Sending MMS picture from Signal on these devices to AT&T (iPhone 6, iPhone 6S, Galaxy S7) reveals that message to the recipient. I can receive MMS images from them. Sending that same MMS picture to a Verizon iPhone 6 works successfully.
I'm having the same issue. Signal installed on OnePlus One, Cyanogen OS 13.1.2, android 6.0.1, AT&T network. I can't download MMS from my brother. He is a Signal user & sends from his iPhone. Here's my debug log: https://gist.github.com/ccb97077f207abef4324004e1c86edd4
@Emu-latte What you described is not the same issue as the title. This issue is for SENDING messages. You can check out the support page for RECEIVING MMS.
@graboskyc and @justin- You may want to attach debug logs. And also test w/ WiFi compatibility mode on.
@riyapenn OK, my bad, I figured AT&T and MMS fail was maybe the same issue. I checked the SUPPORT PAGE FOR RECEIVING MMS thank you anyway, none of that fixes anything.
Actually, the issue is about RECEIVING mms. SEE OP TITLE THX
The issue title and OP describes a Signal user sending MMS to non-Signal user where the non-Signal user (receiver) does not see the MMS. So here the only Signal user is the sender. You described you (Signal user) having issues receiving MMS. contact [email protected] or make sure you edit your APN settings / ask your provider to reprovision your device.
@riyapenn I uploaded the logs. Link is:
https://gist.github.com/48d52032424cf4ad74f2d77d42854c95
After I enabled Wifi compatibility mode, it worked for one phone number and not another. Both AT&T iPhone 6. Toggling the Wifi setting off again and resending the same photo again yielded the error message on the AT&T handset.
Signal 3.24.1 on Android 7.1 when Justin submitted and I posted my first response. Upgraded to 7.1.1 last night.
Same problem and phone/Carrier/OS version/Signal version as the OP. Although it happens a lot, it isn't always reproducible - but it happens enough that it is a really serious problem for me. Sometimes resending the exact same picture will result in its being successfully received. I've not noticed any pattern as to why it works sometimes and other times it doesn't.
Having same issue with both Nexus 5x and 6p on Google Fi. When sending MMS to non-Signal users on AT&T they see an error message that the attachment is not suitable. I can receive MMS messages from them and MMS messages sent to VZW & T-Mobile non-Signal users are received successfully.
However, I've found that:
Signal 3.25.3
Android 7.1.1
Logs - https://gist.github.com/anonymous/b2011978193ebd05871db854ea6829a8
Same problem on Google Pixel running on Google Fi. Images sent from Signal to non-Signal AT&T user results in the OP's error message, both on WiFi and on a cellular connection. Tough bug to deal with, especially since I don't always know which network the recipient is on before I send an image.
Google Pixel
Android 7.1.1
Signal 3.30.4
'WiFi Calling' compatibility mode enabled
Can upload logs later if helpful.
I'm also able to replicate this issue when sending an image via mms from signal on t-mobile to another signal user on at&t. Super frustrating...
TX Carrier| RX Carrier|transport|status
--------------|---------------|------------|---------
Sprint|AT&T|signal|ok
Sprint|AT&T|MMS|ok
TMO|AT&T|signal|ok
TMO|AT&T|MMS|no good
Project-fi WIFI|AT&T|signal|ok
Project-fi WIFI|AT&T|MMS|ok
I'm seeing this as well with Project-Fi. T-Mobile has a 1 MB limit, but I'm not sure if that's the issue here. https://support.t-mobile.com/docs/DOC-5354
I have the same issue as OP.
Using:
Google Pixel
Android 7.1.2
Project Fi
Signal 4.3.2
I'm hoping 51d61445915e0a607742a46c60332e015f9559b6 helps with this. @drawks nice chart by the way!
I'm very happy to report that this appears to be fixed for me with the 4.6.0 update! (Google Pixel, Android 7.1.2, Signal 4.6.0, Google Fi (both cell and WiFi sending).)
Many thanks!
GitHub Issue Cleanup:
See #7598 for more information.
Most helpful comment
I'm also able to replicate this issue when sending an image via mms from signal on t-mobile to another signal user on at&t. Super frustrating...
TX Carrier| RX Carrier|transport|status
--------------|---------------|------------|---------
Sprint|AT&T|signal|ok
Sprint|AT&T|MMS|ok
TMO|AT&T|signal|ok
TMO|AT&T|MMS|no good
Project-fi WIFI|AT&T|signal|ok
Project-fi WIFI|AT&T|MMS|ok