roundabout way;
save the .gif
upload it to google drive
share .gif via hangouts / sms
recipient opens link & it parses it's native viewer to show .gif
^^ This is what I wound up doing to get it to work, as it's one of the few mobile-related annoyances I've yet to find the solution to. Tried everything I could think of, including things that I knew didn't logically even make sense, out of desperation. Tried attaching it as a video rather than an image — no go — tried viewing it as a slideshow — also no go — tried first just finding it in Root Explorer (or any other file manager) then SENDing it to (or SHAREing it with) the messaging app, which didn't change anything. Some other stuff I tried but can't think of right now. But what made me realize how hopeless everything I was trying was when I decided to try saving the GIF first, and then viewing it.
I was thinking that, okay fine, so it doesn't animate when viewed from within the message for some reason, but it should save just fine, and I should be able to view it that way after saving it. Decided to try it by sending it to myself, and if it worked then I could send it with a PS at the bottom telling the recipient that if the GIF appeared as a still image, to please long-press SAVE it and then view it using wtv method was favored by him or her, this until I found a more permanent solution.
So I send it to myself, and when it comes in I set about doing just that : I long-press the GIF, which pops up a 7-item menu — Delete, View slideshow (which doesn't work, as I said), Forward, etc.— and I choose SAVE ATTACHMENT. Up pops a little confirmation dialog which just has the name of the attachment (which is also the file name that will be used to save) and has a little checkbox next to it, and with "Save" and "Cancel" buttons underneath.
I tap the confirmation checkbox, the "Save" button becomes active, and I'm just about to tap it when WHOA-WHOA, WTF? I really see the file name that's about to be used. Let's say the animated GIF is called "weirdcats"; Rather than seeing this as a file name to save under :
weirdcats.GIF
… it actually says this :
weirdcats.
JPG
This was in fact pointed out by someone in this thread, the JPG thing, and it guarantees it isn't a viewing problem, for one thing — the damn thing is being treated as a JPG either (a) right from the start, when it's attached, or (b) in transition, i.e. after SEND is tapped but before it arrives at its destination.
At that point I started going the Google Drive route.
Damn … potential
tl;dr, sorry folks.
THAT SAID, it was mentioned a few posts up that the limit seems to be 1.00 MB and that under that limit they're shouldn't be a problem. The animated GIF attachment I recently tried and failed with was (drumroll) 1.07 MB, or juuuuust over that limit. It would be interesting (and instructive) to see if I would have better luck with the exact same file if I slightly altered its properties first to get it just below 1.00 MB.
So I will …
… and will post the results right here, along with any other pertinent data like whether Wi-Fi on/off made any difference, in just about 24 hrs.
SEE BELOW FOR CONCLUSION
⇓
⇓