Şu anda bakım nedeniyle sitemiz kısıtlı işlevsellik sunmaktadır. Mevcut makaleler sorununuzu çözmediyse ve bize soru sormak isterseniz Twitter’da @FirefoxSupport hesabından ve Reddit’teki /r/firefox subreddit'inden destek gönüllülerimize ulaşabilirsiniz.

Mozilla Destek’te Ara

Destek dolandırıcılığından kaçının. Mozilla sizden asla bir telefon numarasını aramanızı, mesaj göndermenizi veya kişisel bilgilerinizi paylaşmanızı istemez. Şüpheli durumları “Kötüye kullanım bildir” seçeneğini kullanarak bildirebilirsiniz.

Daha Fazlasını Öğren

Images downloaded using firefox (android) not recognised properly - cant attach pics for mms

  • 15 yanıt
  • 31 kişi bu sorunu yaşıyor
  • 3 gösterim
  • Son yanıtı yazan: apixelatedmind

more options

Hey

I have been experiencing a problem on my HTC one x where images downloaded through firefox for android will not behave properly in my phone. Attempts to attach pictures to text messages are met with a pop up saying "unable to attach media".

Inspecting the details of these pictures in the gallery app showed that the file type field is blank (hence being unable to attach it to a mms, another symptom is that gifs display as a still image of the first frame of the gif). Inspecting these pictures using a file browsing app shows that they all have the correct extensions for their file type. Renaming the pictures (without changing the extension) within the file browser seems to fix the problem - their file type shows up correctly within the gallery app, pics can be sent via mms and gifs become animated.

I am only experiencing this issue with firefox, the same images downloaded with different browsers all work perfectly - i dont have to rename them to get my phone to recognize them properly.

The problem may have something to do with the method that firefox uses to download files - every file i have downloaded using other browsers shows up in my phones stock "downloads" app, while files downloaded through firefox do not (it keeps its own list within the app itself)

Any ideas as to the cause of this problem?

Hey I have been experiencing a problem on my HTC one x where images downloaded through firefox for android will not behave properly in my phone. Attempts to attach pictures to text messages are met with a pop up saying "unable to attach media". Inspecting the details of these pictures in the gallery app showed that the file type field is blank (hence being unable to attach it to a mms, another symptom is that gifs display as a still image of the first frame of the gif). Inspecting these pictures using a file browsing app shows that they all have the correct extensions for their file type. Renaming the pictures (without changing the extension) within the file browser seems to fix the problem - their file type shows up correctly within the gallery app, pics can be sent via mms and gifs become animated. I am only experiencing this issue with firefox, the same images downloaded with different browsers all work perfectly - i dont have to rename them to get my phone to recognize them properly. The problem may have something to do with the method that firefox uses to download files - every file i have downloaded using other browsers shows up in my phones stock "downloads" app, while files downloaded through firefox do not (it keeps its own list within the app itself) Any ideas as to the cause of this problem?

Tüm Yanıtlar (15)

more options

How your saving the picture?

Just hold the pic and save image as...


If your getting problem, try with firefox beta.

more options

Holding the pic and choosing save image is the method I am using. this problemm occurs with the beta version aswell as the normal version

more options

Its happening in particular website or all the websites?

Could you provide the sample image

more options

All websites. this problem affects any image i try to download

more options

This works for me using https://en.wikipedia.org/wiki/File:Vanellus_indicus_-_Laem_Phak_Bia.jpg using a Nexus 4. Would you confirm that you have a problem with this image?

more options

yes I still have the problem with that image. I just tried using an old phone, a HTC incredible s, and I encountered the same problem. Maybe the issue is specific to HTC phones?

more options

Talked with a co-worker. This is https://bugzilla.mozilla.org/show_bug.cgi?id=842037

The workaround is to long tap on the image and select share and then choose message.

more options

Thanks for that, good to know that the bug is being worked on.

more options

Hi, I believe I have a similar problem, but it's not with sending MMS pics. If I long tap on a pic , then click "Save Image", it will go into the \download folder. .Firefox will save the jpg file like this "ImageFile.jpg.jpeg" . It keeps adding the extra ".jpeg" at the end past the other ".jpg" and that seems to mess up my stock "Gallery" app. The app will not (see) the image files until I use a file browser and rename the file without the .jpeg on the end. The only .jpg files that it does not do this to are pics downloaded off Facebook using FB's download link.

more options

Hey Its a known bug and has apparently been resolved:

https://bugzilla.mozilla.org/show_bug.cgi?id=712748

have you tried using Firefox beta?

more options

I have an older Beta version. I will update and see how it fares... thanks fuzzy

more options

I have this same problem on a GS4, only happens with firefox, ran beta it didn't change the problem.

more options

I too am having this problem, and even using the latest Firefox Beta does not solve this problem. Again this issue only arises if saving an image from Firefox happens. Using the stock browser, Chrome for Android, and Dolphin Browser this error does not occur.

more options

If you follow the link posted by kbrosnan earlier you can keep track of the bug. It looks like its not being worked on at the moment however, so dont expect it to be fixed any time soon. You can try the "share image" workaround, but that method doesn't work for me.

more options

@fuzzymcfuzzfuzz Yeah I took note of all of that. Just figured that I would point out we are still dealing with this issue is all. Should be a simple fix.