As the title says when I go to try to attach a photo to a post I get an error message with something like ‘Unable to upload photo. Please try again.’ Anyone know how to fix this? For context I’m using the Voyager for Lemmy app on Android

edit: I’ve tried uninstalling/reinstalling the app and perfoming an update for Android with no avail. I’ve emailed support but have not gotten a response. For those curious, using the Lemmy website or the Voyager web app both work fine

  • Sentau@feddit.deEnglish
    6·
    1 year ago

    Check if you can upload images using other clients or the official instance website. Maybe your instance temporarily blocked photo uploads to counter spam

    • WillaGemOPEnglish
      2·
      1 year ago

      I can post using the website. I’m pretty sure it’s a problem with the app

    • just some guy@sh.itjust.worksEnglish
      1·
      1 year ago

      I’m having this issue on iOS 17. It doesn’t appear the instances I’m trying to post to have image uploads blocked as there’s several posts by others with uploaded photos. I was also able to upload to a post, just now, using Memmy

          • aeharding@lemmy.worldMEnglish
            2·
            1 year ago

            Thanks, that’s odd. Upload is working in my tests.

            I can try sh.it just.works to see if it’s a problem there. Otherwise, if you can provide me as much information as possible to reproduce on GitHub (image used would be helpful too) I’d be happy to investigate more!

            • just some guy@sh.itjust.worksEnglish
              1·
              1 year ago

              I was just able to upload an image to Pine64@lemmy.ml from this account (though in a browser) not sure if that will help in determining if the problem does lie with the sh.itjust.work instance. Absolutely! I’ll head over to the github and give as much detail (plus one of the pics I tried to upload) as to the issue as I’ve been encountering it.

  • Cheradenine@sh.itjust.worksEnglish
    2·
    1 year ago

    I am having the same issue. I thought it might be due to image size but I used Imagepipe to reduce it and still got the error.