My parents are having an issue where they are not receiving MMS messages. I was having this issue on Signal Beta on MY OnePlus 6t, so I uninstalled and reinstalled only to be greeted with this issue #9136 which is not a resolved or duplicate issue (@greyson-signal )
Actual result: "Error downloading MMS message, tap to retry", click retry, it spins for a second and then "Error downloading MMS message, tap to retry" again ad infinitum
Expected result: the MMS message downloads
Device: OnePlus 6t & Samsung Galaxy S10e
Android version: Android 9
Signal version: 4.49.16
Carrier: AT&T
This is the link for the debug log for my mom's S10e. That's all I could get at the time of writing this issue
https://debuglogs.org/868b7a7d545287bcf96691fbeb753cf89e44384b1e4fe5b271cba972471e67e1
It might be helpful if you could include the receiver's carrier in the title and device info section. Thanks!
It might be helpful if you could include the receiver's carrier in the title and device info section. Thanks!
That's a good point. We're all on AT&T and I have updated the info to reflect that. Thanks
I have a similar error. See https://github.com/signalapp/Signal-Android/issues/9174#issuecomment-552696434 for more info
I too have this error on a Oneplus 6T on AT&T.
Signal Version 4.49.18
My wife and I are also both getting this error for the past several months. We are on AT&T, she has signal version 4.49.18 on a Samsung galaxy s10 running Android 9, I am using signal version 4.49.18 on a Pixel 3XL running Android 10, but was also having this trouble on android 9 before the upgrade as well. We both use WIFI calling on our devices. MMS usually comes through better while on WIFI but not always. We both have the WIFI calling compatibility enabled inside of signal app.
Prior to collecting the log below, I ran a few tests with users sending me both pictures and regular texts through to our group chat. One thing to note, all messages in a group chat weather they contain images or multimedia or not, appear to come as an MMS rather than an SMS. A couple messages came through ok in the beginning of the log, when I turned WIFI off and was on 4g signal and then the messages failed to come through. I forgot to collect the attempt to get the failed messages once I reconnected to WIFI but even after getting back on WIFI, once a message fails it wont come through unless I fully restart the phone, then I can get 1 and only 1 to come through unless I restart again.
Uploaded logs prior to restart: https://debuglogs.org/6c24f20214aa48e464b149b5243549ba10b16ae7d6afdf44b93b13fdcc5a9bfb
Uploaded logs after restart and 1 successful MMS retrieved, 2 failed attempts:
https://debuglogs.org/03404ac5fe1d87a3081bd0840da7c9e16ab5d48bab8c6c286f4db13d52dacacf
Have been having an issue that resembles this on and off since June. Originally, turning off WiFi worked around it. Recently, that stopped working.
Details: MMS not downloading ('error downloading MMS; tap to retry')
Occurs: when receiving an image from a non-Signal user using an iPhone.
Sending images works.
MMS downloads from non-Signal user using Android.
Standard messaging app works fine.
My carrier: AT&T
Phone: LG Phoenix 4
Friend's carrier: ? (WILL UPDATE)
My version: 4.49.18.
Android version: 8.1
Not sure if this is the same issue, but looks like it.
https://debuglogs.org/bac8b22a7e8bde4d71117b85468b9e89467b0f06959a396acc02d48ad93a79c6
All my ATT friends seem to also have this problem. I guess we will be using for Signal for IM only for a while. I hope yall can fix this because we need our default app to be reliable.
Friends phones that are having this issue: Moto G6 Plus (Cricket), Note 8 (ATT), S8 (ATT), S9 (ATT), Pixel 3a (ATT), OnePlus 6T (ATT). (All on the latest update for their OS and Signal).
It seems that we have found a common thread, thanks @Cerberus0
I like others are seeing the same issue on AT&T, Signal 4.49.18. I have a group text that has approx 10 people on it spread across all of the carriers including AT&T, Tmobile, Verizon and Google Fi.
Group messages are being delivered to the main thread but it appears that they are also attempting delivery to the individual contact which fails with the same error as others.
At at point it seems to be isolated to the ppl on the chain using AT&T.
@Tursko suggested I provide this ink to my debug log which is from an attempt to download one of several MMS messages (which are most likely just text) sent from non-Signal users (AT&T iPhone users) to a group that I'm in. https://debuglogs.org/1065bd97a8eb1f39bbcedda5f91b5a74e0ff562c924e284b33ca90275d829c36
We're also all on AT&T.
Same problem here. Note 9 on AT&T / FirstNet. Happens frequently since 10/30.
https://debuglogs.org/37c745d9fa60b850c9af356be9e4f3d6f116f2e8cbd90cd1c32f4d8ba13f9de9
Same problem on Pixel 3, AT&T, Signal 4.49.18
Hey I am having an issue as well on my Samsung j7. Carrier is AT&T only person in my friend and family group using Signal. Both Android and Apple user sent messages fail. The issue sprung up like two weeks ago for me. https://debuglogs.org/1a72dd9d5fe51691feb8222fde8e49b959fa1e692da5c02356d2342eb0c5daaf
I have the same problem (Pixel 3, AT&T, Signal 4.49.18)
I have had to switch away from Signal. . .privacy only matters when you actually get messages :-(
Log link: https://debuglogs.org/c722fe55d7bac7373a1d27e9a097b8e6cd46fc7647a041b6b9fbc3023781dc54
S7, AT&T, Signal 4.50.2
I have had to switch away from Signal. . .privacy only matters when you actually get messages :-(
Log link: https://debuglogs.org/c722fe55d7bac7373a1d27e9a097b8e6cd46fc7647a041b6b9fbc3023781dc54
S7, AT&T, Signal 4.50.2
Your messages are only private if it’s a Signal IM. This issue is related to the SMS portion of the app. Please explain the issue you are having.
I think what @Tursko means is that the whole point of using Signal is that it allows for encrypted messaging, which is why nearly all of us installed it. That said, what made Signal different from all the other encryption messaging apps was that it could also be used as our everyday SMS/MMS client, as well....and it was THIS selling point that made convincing others to adopt it a no-brainer. ATT is one of the largest cellular providers out there and if nearly a third of US non-Signal users are sending me MMS and I can't receive or retrieve them, then that does away with a substantial reason to continue to use it. If I am going to have to continue to suffer through inconvenience, then I may as well convince others to switch to Conversations for encrypted communications and go back to the stock messaging app for SMS/MMS. While it will also be inconvenient, at least I will get all my messages. The new dashboard showing the percent of adopters in my contact list is serving a purpose Signal never intended. . .For me, it is showing me how many are dropping Signal because of this issue. I have been with Signal since the TextSecure days, but the inability to either have the MMS issue fixed or run it as a standalone encrypted communications app, means my days of being an evangelist and user of Signal are coming to a close, I fear.
I think what @Tursko means is that the whole point of using Signal is that it allows for encrypted messaging, which is why nearly all of us installed it. That said, what made Signal different from all the other encryption messaging apps was that it could also be used as our everyday SMS/MMS client, as well....and it was THIS selling point that made convincing others to adopt it a no-brainer. ATT is one of the largest cellular providers out there and if nearly a third of US non-Signal users are sending me MMS and I can't receive or retrieve them, then that does away with a substantial reason to continue to use it. If I am going to have to continue to suffer through inconvenience, then I may as well convince others to switch to Conversations for encrypted communications and go back to the stock messaging app for SMS/MMS. While it will also be inconvenient, at least I will get all my messages. The new dashboard showing the percent of adopters in my contact list is serving a purpose Signal never intended. . .For me, it is showing me how many are dropping Signal because of this issue. I have been with Signal since the TextSecure days, but the inability to either have the MMS issue fixed or run it as a standalone encrypted communications app, means my days of being an evangelist and user of Signal are coming to a close, I fear.
Yep, SMS/MMS support is a huge selling point for me as well. So hopefully this issue can be fixed.
Agree with the several posts above. I can't articulate any better how important this bug is to get fixed ASAP for market share retention. AT&T being the top if not second from top provider in the US means this doesn't work for many users if they've noticed or not. I'm sure everyone doesn't know to come here to post a bug report so it's hard to quantify the scope of the problem. I'm now on 4.50.3 an still a problem.
I have a Samsung S8 AT&T using Signal version 4.49.18 & Android 9 and when my friend messages me a photo or MMS, it gives me the same error ;-; https://debuglogs.org/ec8ed42363ae71b3fc4470e4744fe28380c48ab61aa17d10d2995ddb0a1d7be6
I know for a fact that Greyson has seen this issue so I'd assume that they are looking into it. He closed a couple of duplicate issues last week. Obviously, if it was something small it would already be fixed.
Been experiencing this issue for a while now and just found this thread. Note 10+, Android 9 and on ATT. This has been an ongoing issue for me crossing two different phones. Been frustrating at best... Nearly demolished the phone at the worst. I've switched back to Samsung Messages until this gets fully resolved.
https://debuglogs.org/fe7d16c3c1298f6f57c79dcbfcdadebaf73b4719dae595433afe7f7012ed8407
I am also having this issue on AT&T with a S9+
same issue here for months
AT&T
Samsung Galaxy 9+
SM-G965U
Android v9
Kernel 4.9.112-16352124
Signal 4.49.18
@Tursko @g2bb Has anyone from AT&T responded to this or do they know about it?
@Tursko @g2bb Has anyone from AT&T responded to this or do they know about it?
The extent of my knowledge of this bug is basically inside this Github Issue. All I know is that the Signal team has seen it.
@Tursko @g2bb Has anyone from AT&T responded to this or do they know about it?
The extent of my knowledge of this bug is basically inside this Github Issue. All I know is that the Signal team has seen it.
That is correct. I haven't submitted any bug report to AT&T because, as I see it, it's not their job to make sure they support every SMS app. That would be asking a LOT of them given how many there are. That said It may still be good to mention it to them.
@Tursko @g2bb Has anyone from AT&T responded to this or do they know about it?
The extent of my knowledge of this bug is basically inside this Github Issue. All I know is that the Signal team has seen it.
That is correct. I haven't submitted any bug report to AT&T because, as I see it, it's not their job to make sure they support every SMS app. That would be asking a LOT of them given how many there are. That said It may still be good to mention it to them.
Ok, I am an #attemployee (but not in mobility) so I'll see if anyone is aware of the issue, since, ya know, it's affecting me too..lol.
@Tursko @g2bb Has anyone from AT&T responded to this or do they know about it?
The extent of my knowledge of this bug is basically inside this Github Issue. All I know is that the Signal team has seen it.
That is correct. I haven't submitted any bug report to AT&T because, as I see it, it's not their job to make sure they support every SMS app. That would be asking a LOT of them given how many there are. That said It may still be good to mention it to them.
Ok, I am an #attemployee (but not in mobility) so I'll see if anyone is aware of the issue, since, ya know, it's affecting me too..lol.
Awesome, thanks!
Now if only we could get someone from Signal to reply, like @greyson-signal or @alan-signal nudge nudge
Ditto here (and my wife, who will jump back to the native SMS app shortly if not resolved).
Device : Google Pixel 3 (blueline)
Android : 10
App : Signal 4.50.4 (5702)
https://debuglogs.org/16cd85d4102c1fdd0aad3418bfe740410240143ff83240b2bd771905b57fa01d
Same issue as described above with iPhone MMS to Android Signal messengers. With Signal set to be used as default SMS/MMS app on android device.
Going on now for 1-2 months. (Oct-Nov 2019)
My Carrier: AT&T
My Phone: Pixel 1
Signal version: 4.49.18
Android version: 10
Friend's Carrier: Xfinity Mobile (aka Verizon)
Friends Phone: iPhone 8 using Apple Message app (iphone SMS/MMS default app)
One thing interesting that I did today was I disconnected from WiFi after a failed MMS message and had friend send again just on AT&T and MMS came through, then reconnected WiFi and had them send another message and then that message also succeeded.
So maybe something in the hand-off while traveling when device jumps between WiFi and carrier service.
Ditto here (and my wife, who will jump back to the native SMS app shortly if not resolved).
I've already switched back. I'm keeping the app to see if it updates.
And in reference to downtime0, I've done the same thing as you with the same results (friend's iPhone 8 and Verizon as well). There must be something lost in the reconnect.
I looks like they are well aware and likely working on a fix. I have the same issue on ATT Android 9 using SSGS9. Subscribed and watching for a fix. Thanks for everyone's hard work on Signal!
It's very interesting that a reboot of the phone will let exactly one message download, but a second message requires another reboot to download it. I would love to see a technical explanation of this from the signal team once they figure it out, mostly for my own curiosity.... So weird!
Followup from message above:
Updated on Friday to the "Big" update with Insights vs 4.50.5, and nothing but failed MMS messages all weekend regardless of reboot or toggling between wifi and AT&T carrier service. Switched back to QKSMS app for now, will continue to monitor with Signal contacts only. I really hope this is resolved soon.
Same Issues.
Samsung S7
ATT
However my issue seems erratic.
Sometimes i receive MMS sometimes i do not. (often more "nots")
Until today all my sending ones seem fine, however over the last 24 hours i have an issue sending as well.
The only change i knowingly made was turning on "wifi calling" through S7 android, and mucking back and forth with air plain mode .
Samsung Note 8 on AT&T.
Same issues. FWIW, the MMS errors appear to be more consistent with Apple users.
However I also noticed that when I receive an MMS successfully in a group message, I receive the MMS error message when the other recipients view it. This is received directly from the user, not via the group thread.
Adding my name to the list of users with this issue. First I have a Google Pixle 3XL (OS version 10), AT&T service, Wi-Fi Calling Enabled, and the wi-fi option turned on with Signal. Before going down the path of the App being the issue, I have contacted, and spent many an hour with AT&T as I thought it was related to some previous network issues I had been troubleshooting with the, We went through several tests, including altering my APN from the default AT&T to a custom APN that the AT&T engineer gave me. None of these issues resolved.
Switching off of wi-fi to cellular worked sometimes. Switching to Wi-Fi fixed the issue, sometimes. Hard rebooting the phone fixed the issue, sometimes. There is no consistent methodology to what works and what does not. I can have the issue on pure cellular with no wi-fi spots around at all, and I can have the issue when I have zero cellular service with only Wi-Fi. For the times where I hard reboot the phone, I can go in to Signal, select an MMS message, click to re-download, and it comes through (sometimes), but none of the other messages download for the same contact or others, so I have t go through the process to reboot the phone repeatedly to get the messages.
Also have the same (random) issue when sending MMS messages to non-signal users.
Adding my name to the list of users with this issue.
I enjoyed reading your bug report. I love that you kept track of all those possibilities. The single successful message and subsequent failure of everything after a reboot was my experience too. I believe it is a key to solving this. There is likely a mismatch in the interpretation of the MMS protocol, by the software engineers, either at AT&T or at Samsung. Let's start a pool for whoever identifies the problem. I'll throw in $50 of Bitcoin.
Figured I'd chime in and report similar MMS failures on Pixel 3a running 10, signal version 4.50.6, on AT&T.
@alan-signal @alex-signal @jlund-signal @geogriff-signal @greyson-signal or literally anyone at signal, can we please get some eyes on this issue? It's seriously impeding my ability to work in a group, which is especially important right around finals time. Plus I'm SUUUUUPER sick of my parents bothering me about how they keep missing messages. This is a seriously annoying bug, and it's been nearly a month and we still have no comments or any acknowledgment of the bug from you guys.
https://debuglogs.org/7fb26b571a9436c0276e1603b027d4f7771735cd1c95fda3c50ee48d3b2c0cf5
another OP6 (and OP3T via wife) who can only get one picture message every once in a while by toggling data/wifi/rebooting. No consistent fix found.
Absolutely prevents me trying to advocate Signal to friends and family. I'll stay faithful because images aren't that important (and there is no shortage of ways to share) but for people with little patience this is a deal-breaker.
My wife and I both use OnePlus 5T (me using Lineage and her on stock) on AT&T with latest Signal from Play and experience this issue incessantly, but not consistently (more fails than successes), with family group chats. We can't get everyone to switch to Signal, which is a hard sell when it's apparently a Signal issue, so dealing with mixed client MMS is a fact of life. We've been using Signal for years and won't change, but it sure would be nice to know that Signal devs are working on fixing these issues with MMS on AT&T. Thanks Signal folk, if you're reading, for your help.
Another repro from #9241: https://debuglogs.org/1ebe6780c56147cb85f0c602475d9f2dfcfed4e88f729a13b7d2a704f48f45d4
Note that the MMS service messages I caught using ADB is showing that the AT&T MMS server is returning a "precondition" error. Could this perhaps be the reason why the file handle isn't valid? Unfortunately the server isn't really showing what field is missing.
Update
Samsung galaxy s7
Att
So if I turn off wifi calling, VPN, mobile data.. It seems to work
Same:
OnePlus One
Android 9
Signal 4.50.6
And a bump to the user retention issue. Using it as the default messaging app is the point.
The new beta was released. I don't see anything related to this fix, but has anyone tried it?
Setting configOverrides to null in https://github.com/signalapp/Signal-Android/blob/544b75a2a7fb75256a946e03f698b581f225f7d4/src/org/thoughtcrime/securesms/mms/IncomingLollipopMmsConnection.java#L105 finally made my MMS download after retrying. Not sure what that means, there are about 33 config overrides being sent in my case with Straight Talk
Bundle[{httpSocketTimeout=60000,
aliasMinChars=2,
smsToMmsTextThreshold=-1,
enableSMSDeliveryReports=false,
maxMessageTextSize=-1,
supportMmsContentDisposition=true,
enabledTransID=false,
aliasEnabled=false,
supportHttpCharsetHeader=false,
allowAttachAudio=true,
smsToMmsTextLengthThreshold=-1,
recipientLimit=10,
uaProfTagName=x-wap-profile,
aliasMaxChars=48,
maxImageHeight=1944,
enableMMSDeliveryReports=false,
userAgent=,
mmsCloseConnection=false,
config_cellBroadcastAppLinks=true,
maxSubjectLength=40,
httpParams=,
enableGroupMms=true,
emailGatewayNumber=,
maxMessageSize=1048576,
naiSuffix=,
enableMMSReadReports=false,
maxImageWidth=2592,
uaProfUrl=,
enabledMMS=true,
enabledNotifyWapMMSC=false,
sendMultipartSmsAsSeparateMessages=false,
sim_country_iso_override_string=,
enableMultipartSMS=true}]
Here's the difference in requests
With overrides
2019-12-04 16:43:30.869 5159-18683/com.android.phone I/MmsService: [DownloadRequest@8b3b6e5] Using APN [type=default,mms,supl mmsc=http://mms-tf.net mmsproxy=mms3.tracfone.com mmsport=80 name=Net10 apn=tfdata bearer_bitmask=0 protocol=IP roaming_protocol=IP authtype=-1]
2019-12-04 16:43:30.870 5159-18683/com.android.phone D/MmsService: [DownloadRequest@8b3b6e5] HTTP: GET http://166.216.198.5[51], proxy=mms3.tracfone.com:80, PDU size=0
2019-12-04 16:43:30.872 5159-18683/com.android.phone I/MmsService: [DownloadRequest@8b3b6e5] HTTP: IPv4 provisioned
2019-12-04 16:43:30.872 5159-18683/com.android.phone I/MmsService: [DownloadRequest@8b3b6e5] HTTP: User-Agent=
2019-12-04 16:43:30.872 5159-18683/com.android.phone I/MmsService: [DownloadRequest@8b3b6e5] HTTP: UaProfUrl=
2019-12-04 16:43:31.060 5159-18683/com.android.phone D/MmsService: [DownloadRequest@8b3b6e5] HTTP: 412 Precondition Failed
2019-12-04 16:43:31.061 5159-18683/com.android.phone D/MmsService: [DownloadRequest@8b3b6e5] MmsNetworkManager: release, count=0
Without overrides
2019-12-04 16:45:59.769 5159-18683/com.android.phone I/MmsService: [DownloadRequest@3b7bc2f] Using APN [type=default,mms,supl mmsc=http://mms-tf.net mmsproxy=mms3.tracfone.com mmsport=80 name=Net10 apn=tfdata bearer_bitmask=0 protocol=IP roaming_protocol=IP authtype=-1]
2019-12-04 16:45:59.770 5159-18683/com.android.phone D/MmsService: [DownloadRequest@3b7bc2f] HTTP: GET http://166.216.198.5[51], proxy=mms3.tracfone.com:80, PDU size=0
2019-12-04 16:45:59.772 5159-18683/com.android.phone I/MmsService: [DownloadRequest@3b7bc2f] HTTP: IPv4 provisioned
2019-12-04 16:45:59.773 5159-18683/com.android.phone I/MmsService: [DownloadRequest@3b7bc2f] HTTP: User-Agent=LineageOS
2019-12-04 16:45:59.773 5159-18683/com.android.phone I/MmsService: [DownloadRequest@3b7bc2f] HTTP: UaProfUrl=http://www.google.com/oha/rdf/ua-profile-kila.xml
2019-12-04 16:45:59.881 29208-29336/com.thetileapp.tile D/BluetoothAdapter: isLeEnabled(): ON
2019-12-04 16:46:00.262 5161-5161/? I/wpa_supplicant: wlan0: CTRL-EVENT-AVOID-FREQ ranges=
2019-12-04 16:46:00.262 276-5327/? I/WifiHAL: event received NL80211_CMD_VENDOR, vendor_id = 0x1374, subcmd = 0xa
2019-12-04 16:46:01.022 5159-18683/com.android.phone D/MmsService: [DownloadRequest@3b7bc2f] HTTP: 200 OK
2019-12-04 16:46:01.050 5159-18683/com.android.phone D/MmsService: [DownloadRequest@3b7bc2f] HTTP: response size=60
2019-12-04 16:46:01.050 5159-18683/com.android.phone D/MmsService: [DownloadRequest@3b7bc2f] MmsNetworkManager: release, count=0
Maybe this commit https://github.com/signalapp/Signal-Android/commit/53e0dc5deed567e929af89566c05a7b98990e0e4 fixed mms for some, but broke mms for others
I'm running 4.50.6 and I have the same issue. I was at the car dealer last week and needed to send an image (screen shot) of my paycheck from my work phone to my personal phone to the bank as the bank needed it to come from the email they had on record. I had to reboot my personal phone twice before the MMS would download. Then just this morning I got a group text and it was working, but one of the messages wouldn't come through. Turns out it was an iMessage who hit the like on the text. Restarted the phone twice just to fine out it was a stupid "like". How frustrating.
Hello! Looks like @yate has a potential fix for this issue in #9249. If anyone is interested in trying it out, I can sign a build and send it to you. That means that it could install in-place over your existing installation.
If this is something you want to try, you can message my test number on Signal at +1 610 708 0800.
Hello! Looks like @yate has a potential fix for this issue in #9249. If anyone is interested in trying it out, I can sign a build and send it to you. That means that it could install in-place over your existing installation.
If this is something you want to try, you can message my test number on Signal at +1 610 708 0800.
This seems to be much better. Only been testing less than a day but haven't had a single failure yet (from Android or iPhone peeps). Thanks to @yate and @greyson-signal
Hello! Looks like @yate has a potential fix for this issue in #9249. If anyone is interested in trying it out, I can sign a build and send it to you. That means that it could install in-place over your existing installation.
If this is something you want to try, you can message my test number on Signal at +1 610 708 0800.This seems to be much better. Only been testing less than a day but haven't had a single failure yet (from Android or iPhone peeps). Thanks to @yate and @greyson-signal
Sounds great!! What is the back time for this to go live?
Messaged number, haven't heard back?
Get Outlook for Androidhttps://aka.ms/ghei36
From: John Mautz notifications@github.com
Sent: Saturday, December 7, 2019 9:33:00 AM
To: signalapp/Signal-Android Signal-Android@noreply.github.com
Cc: ArchmageArcane rkmage@hotmail.com; Comment comment@noreply.github.com
Subject: Re: [signalapp/Signal-Android] Not downloading MMS messages in group chats or single person chats on AT&T (#9173)
Hello! Looks like @yatehttps://github.com/yate has a potential fix for this issue in #9249https://github.com/signalapp/Signal-Android/pull/9249. If anyone is interested in trying it out, I can sign a build and send it to you. That means that it could install in-place over your existing installation.
If this is something you want to try, you can message my test number on Signal at +1 610 708 0800.
This seems to be much better. Only been testing less than a day but haven't had a single failure yet (from Android or iPhone peeps). Thanks to @yatehttps://github.com/yate and @greyson-signalhttps://github.com/greyson-signal
Sounds great!! What is the back time for this to go live?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/signalapp/Signal-Android/issues/9173?email_source=notifications&email_token=ANYC4EBUQTYUAHC2H6LN57LQXOXZZA5CNFSM4JLB2UC2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEGGIBMA#issuecomment-562856112, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ANYC4EHUW4HTWK6LW7PRQBTQXOXZZANCNFSM4JLB2UCQ.
Same
I've been using the patched version from @greyson-signal heavily since yesterday, no MMS errors in a chat where 50+% of them were errors on the live build. Pixel 4 XL, ATT, Android 10.
Same here, had a ton of chatter in one of my large MMS threads and all of the inbound messages succeeded. I even compared my messages to another guy on the thread and all the messages matched.
Patched version has worked flawlessly for me so far—installed it about 48 hours ago.
I installed a self signed version on my Galaxy S9+ (FirstNet) 5 days ago and greyson's version on my girlfriend's Galaxy S10e (AT&T) 2 days ago and all group MMS have worked since. It certainly seems to have fixed the issue. Thank you for the contribution @yate
I'm still having issues with the one greyson-signal signed. Still having issues with sending and receiving MMS.
Using StraightTalk on the AT&T network on OnePlus 6T.
@Charles08 I've never had any problems sending MMS, only receiving. Would you be able to post a logcat and your APN settings?
@Charles08 It seems to be timing out trying to download, so I don't think my change would work for you. You can try my APN settings if you would like. They are the unmodified settings from LineageOS.
@Charles08 It seems to be timing out trying to download, so I don't think my change would work for you. You can try my APN settings if you would like. They are the unmodified settings from LineageOS.
Thanks for looking at the logs and your apn settings. I mirrored mine to yours and now my mms works on the latest signed build. Sweet!
Anyone know how close to release this is? I was getting killed on unreadable messages and had to go back to default Android messages. I'd really like to get back to business with signal. I requested the test build that seems to work, but I never got a response. Let's just get this fixed....
I just got 4.51.6 pushed to my phone this morning from the Play and about 3 hours latter I received my first group text from who I know is an iPhone iMessage users and it fails to download the MMS. I will have to reboot my phone to get the message. Sigh, I had high hopes. Maybe this is not the version with the fix.
No love in 4.51.6...
The PR #9249 is still open so it hasn't been baked into the beta releases yet, only the pre-beta that a few of us are using. @greyson-signal, given your abundance of time, do you have an ETA of when this PR will be accepted?
I'm sure a bit more testing is required before he can merge the PR. I'm glad that it is working for all of y'all though!
The test build is working great! I even got an MMS with 7 pictures and they all downloaded fine.
Hello,
Can anyone confirm (on the build mentioned 'working '). That when wifi calling, VPN, and on att network still receives mms?
If you're using 4.51.5-att-fix and have working MMS like I did, then DO NOT upgrade to 4.51.6 from the Play store else you'll lose your working MMS and won't be able to reinstall the 4.51.5-att-fix over 4.51.6 from Play. sigh
Hello,
Can anyone confirm (on the build mentioned 'working '). That when wifi calling, VPN, and on att network still receives mms?
MMS working for me when connected to my OpenVPN connection while on ATT LTE. Att doesn't support my OnePlus 6T for wifi calling.
Hey guys, experiencing this issue as well on T-Mobile's network. I see a fix is in the works, but figured I'd share my debug log just in case it's helpful:
https://debuglogs.org/6330909a439146a00bc99a968b2c34c21bab0349e9b15428aa4269e9734b9f88
What about those of us on Verizon?
On December 12, 2019 6:28:55 PM CST, IrkenEngineer notifications@github.com wrote:
Hey guys, experiencing this issue as well on T-Mobile's network. I see
a fix is in the works, but figured I'd share my debug log just in case
it's helpful:https://debuglogs.org/6330909a439146a00bc99a968b2c34c21bab0349e9b15428aa4269e9734b9f88
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/signalapp/Signal-Android/issues/9173#issuecomment-565248511
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
Hello! Looks like @yate has a potential fix for this issue in #9249. If anyone is interested in trying it out, I can sign a build and send it to you. That means that it could install in-place over your existing installation.
If this is something you want to try, you can message my test number on Signal at +1 610 708 0800.
What about those of us on Verizon?
…
On December 12, 2019 6:28:55 PM CST, IrkenEngineer @.*> wrote: Hey guys, experiencing this issue as well on T-Mobile's network. I see a fix is in the works, but figured I'd share my debug log just in case it's helpful: https://debuglogs.org/6330909a439146a00bc99a968b2c34c21bab0349e9b15428aa4269e9734b9f88 -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: #9173 (comment)
-- Sent from my Android device with K-9 Mail. Please excuse my brevity.
Greyson created a test build. If you're interested you could install it on your device and see if it fixes the issue.
@IrkenEngineer Your issue is different and it is likely to be an APN issue. I would verify your settings with the "Android APN Settings" section here https://support.t-mobile.com/docs/DOC-2090
Hello! Looks like @yate has a potential fix for this issue in #9249. If anyone is interested in trying it out, I can sign a build and send it to you. That means that it could install in-place over your existing installation.
If this is something you want to try, you can message my test number on Signal at +1 610 708 0800.
Any chance you will send this build over here. I can't take this anymore not receiving mms. My sister and gf both stopped using signal because of this. Is there a link you could post here to download or is that against the rules or something?
I have been having this issue also, tried the workaround of restarting right after clicking "tap to retry". It works. Hopeful for a fix soon. AT&T, Signal v4.51.6. Galaxy S6 Active (SM-G890A), Android 7.0.
Hello! Looks like @yate has a potential fix for this issue in #9249. If anyone is interested in trying it out, I can sign a build and send it to you. That means that it could install in-place over your existing installation.
If this is something you want to try, you can message my test number on Signal at +1 610 708 0800.Any chance you will send this build over here. I can't take this anymore not receiving mms. My sister and gf both stopped using signal because of this. Is there a link you could post here to download or is that against the rules or something?
Message that number. Greyson said to send him a text asking for the test build that fixes MMS.
I am having this issue. It's so bad that i have decided to switch away from signal until it is fixed. I am on Android 7.0, Galaxy S6, on ATT.
Most MMS messages (including group messages) do not come in. They give me an option to redownload but it never succeeds. This is an app-breaking bug. A friend of mine is having the same issue and he too has now switched off Signal :/
Hopefully, it will be fixed soon. Greyson has a signed test build that has a possible fix.
I have had perfect success with the apk from @greyson-signal that includes the fix from @yate and it hurts to see so many of you still suffering and ditching Signal. I can't blame you and it really tempts me to post a link to the apk for you guys. Ugh. I know it's the holiday season and Signal guys may be busy with family life, but Signal users are suffering and their advocacy toward potential users is more than nullified when they have to stop using Signal themselves. It's a bad situation. 😟
Don't get me wrong, I love the work from Signal devs and wouldn't stop using Signal myself, but I can appreciate the more intense pressure some of you are under from friends, family, and significant others who don't grok the need or desire to protect privacy. It's hard to get them on board in the first place and then having to come clean that it's the app you want them to use that is the culprit makes it so much harder to convert them. Ugh again.
I finally dropped it. Just too many Apple people or MMS groups that message me. I messaged greyson twice over 2 weeks with no response. I know a lot of people less technical than us (they don't even know what github is) that are just ditching it for good. Pretty sure people like that won't come back even when it's fixed. Really too bad if there's a fix that actually works, but nobody around to roll it to production.
They aren't going to put a pull request in a stable release that just came out. It needs to be tested and verified first.
Once they fix the issue just try to convert your friends back. I told my friends to just use Signal for Signal only and then their default messaging app for SMS/MMS until Signal fixes it. If the bug was easy to fix it would have been fixed a month ago. Luckily @yate may have solved it. Now just let Greyson and the Signal team integrate and properly release it (if its the proper solution).
BUT I can understand yalls frustration, I do feel like this should be a #1 priority since its a piece of the core functionality.
Me too.
AT&T, Pixel 3
https://debuglogs.org/717bc31d2b839acda91136205f111c360883285445ae4495e3d145882cf91539
Hey folks, here's an update:
So we're looking to ship this fix in 4.52, which is going to beta very soon. Thank you!
Amazing news. Thanks @yate & @greyson-signal !
I can't wait to send out my mass text saying, "you can now set Signal as your default again!"
So I installed version 4.52.1 from apkmirror.com and I am still getting this problem.
Pixel 3, AT&T, receiving group text from iPhone user.
Debug log: https://debuglogs.org/051c4afb5e343c08195179680599258816297d4fde0b307725450f61bbdc09d2
If anything, the situation seems worse than before, because before, I could tap the message, restart the phone, tap the message again, and the message would then download and appear correctly, but that is now not working.
I also seem unable to send group texts (to non-signal users); likely unrelated but I mention it because you may see this in the debug log.
Screenshot:
It might be worth it to post it directly on the beta thread https://community.signalusers.org/t/beta-feedback-for-the-upcoming-android-4-52-release/10643/45
@dtenenba Given that 4.52.x seemed to fix everyone else's AT&T MMS problems, I'm going to assume you're experiencing a separate issue -- especially if you're having problems sending. I'd open up a separate issue.
MMS downloading with beta 4.52.1
First time it's worked for me in months.
@greyson-signal I think you are correct. I was having MMS problems regardless of my texting app, straightened it out with a call to AT&T tech support. Have not yet re-verified that Signal works for me but will do so soon.
This is absolutely not "fixed".
Att
Android
VPN
Wifi calling
Samsung
Every other texting app MMS works under these conditions except signal.
Edit: other apps- samsung messages, Google messages, textra, messenger, color messages...
All tested then uninstalled. Full restart reinstall of signal, full restart still not working.
@ProNoob333 please open a separate bug report. Make sure to fill out the issue template and include a debug log. Without it, it's really hard to figure out what's going on.
One thing you could try before that, though, is to toggle Signal's "WiFi calling compatibility mode" setting under "SMS and MMS".
As someone who is now running beta - it DOES appear to be fixed and i'm quite happy.
@ProNoob333 please open a separate bug report. Make sure to fill out the issue template and include a debug log. Without it, it's really hard to figure out what's going on.
One thing you could try before that, though, is to toggle Signal's "WiFi calling compatibility mode" setting under "SMS and MMS".
It is on and totally not working...
Edit: someone says "beta is" I do not know what that means. I am commenting on the version available in Google play store.
Edit2: @haffenloher I'm not opening up another report it's the same issue. I will just delete the app and advise my friends having the same issue to give up also. Cheers - and good luck.
@ProNoob333: This issue should be fixed in version 4.52. You can check your app's version number by going to Signal Settings > Advanced. The developers are most likely doing a staged rollout, so if you're still on 4.51 and can't wait to get this update, you can join the beta here.
As @haffenloher said, it's impossible for anyone here to figure out what's going on on your device unless you can share a debug log. Immediately after receiving a failed MMS, go to Signal Settings > Advanced > Submit debug log > tap Submit > tap and hold to copy the URL > paste the URL here.
What version do you have? 4.51.x didn't work with MMS. 4.52.x does.
Get Outlook for Androidhttps://aka.ms/ghei36
From: ProNoob333 notifications@github.com
Sent: Saturday, December 21, 2019 8:16:15 PM
To: signalapp/Signal-Android Signal-Android@noreply.github.com
Cc: ArchmageArcane rkmage@hotmail.com; Comment comment@noreply.github.com
Subject: Re: [signalapp/Signal-Android] Not downloading MMS messages in group chats or single person chats on AT&T (#9173)
This is absolutely not "fixed".
Att
Android
VPN
Wifi calling
Samsung
Every other texting app MMS works under these conditions except signal.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/signalapp/Signal-Android/issues/9173?email_source=notifications&email_token=ANYC4EBILQJNVWWKVH6HEH3QZ25V7A5CNFSM4JLB2UC2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEHPGU2I#issuecomment-568224361, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ANYC4ECJHTDCTEXW3UXQLNTQZ25V7ANCNFSM4JLB2UCQ.
Happy day! Works for me on AT&T on 4.52.4! <3
This is not working for me on 4.53.7
Same issue as previous.
AT&T
Samsung s9.
Logs were previously attached to #8571
Additional log from today here: https://debuglogs.org/c2eb8b7110fb8708d269c819277d9281a06d067292cd48d266fc7f44cb7adf73
Most helpful comment
Hey folks, here's an update:
So we're looking to ship this fix in 4.52, which is going to beta very soon. Thank you!