I wanted to post screenshots of my riced KDE setup on Unixporn so I copied them to my phone using a USB cable. And now when I’m trying to add them to a post, it seems to always show the same error (Client request(POST https://lemmy.ml/pictrs/image) invalid: 403 . Text “<…”). The app has all the required permissions granted and I’m not banned from the community. What can it be then?
Which version?
0.0.59 from F-Droid
I tried different ones. Some are 300-400 kb and one is a bit more than 1 mb
which android version? Lemmy and many others had their pictures upload turned off for a while but I do assume that is enabled again.
I assuming you don’t have android studio or something to see the full logs?
I really need to get that log viewer finished.
Android 13. I believe Unixporn does have image upload turned on. I’m not sure about the instance though. I am a bit familiar with Android Studio but don’t have it installed on any machine now
@dessalines@lemmy.ml Do 403s from pictrs only come from failed authentication? or does it lump all failed requests under 403 such as bad format, image size?
I’d have to double check, but I believe it’s all errors. That could be size-related.
Hmm the images had an uncommon resolution of 1366*768 I think. And I just noticed none of them have the width/height numbers in their metadata. Could any of that be the reason?
If this image uploads it’s probably something else
It did upload correctly
Hmm it could still be a permission issue but that would be on ourside to fix. Did you save this image in the same place as the others? If so can you try that. It might be that we don’t ask correct permission on Android 13.
Tried moving the photos from Pictures to DCIM/Camera and rebooting the phone. Still the same error. Fun fact: if I revoke the app’s permissions and try to upload a photo again, the error remains the same and the app doesn’t ask to grant the permission (the pop-up doesn’t appear)
Wym same error? I meant the above picture that uploads fine. Does it still work after you move it to the location of the picture that doesn’t work.
By default it saves the picture in location that should always be accessible by Jerboa
It is very possible that we don’t properly handle it when it fails to receive permission. I’ll take a look at it.
That shouldn’t be a problem, pictrs shouldn’t be looking at the metadata.
