Awesome update! But I’m getting a status code for all images. I’m posting a picture to hopefully help. Thanks!
You must log in or register to comment.
Update: I opened and closed the app a few times, and couldn’t reproduce it. Maybe it was just a one time thing.
502 is usually from a site rate limiting you for some reason. If it’s a site that hosts a lot of images as you scroll it’s possible it just got too many requests at once or too many in rapid succession.
If it works again, then it was indeed most likely an error of the server that hosts the images.
When images fails to load, there is often nothing I can do. I added these messages to at least indicate why an image doesn’t load. When an image fails to load, you can always press it and then it opens the image in the browser. That way you can verify if it’s a problem with Lemma, or if the image just doesn’t work at all (:
Could mean that the app is pulling full-sized images instead of thumbnails or is pulling the same image multiple times, or it could just be a lower traffic site that can’t handle requests as well as some larger hosting sites
502 is not a rate limiting response. That would be 429. 500-level codes are for server errors. But of course that’s all just convention and you can design a crappy API to use whatever code you want.
If you get a bad gateway response it’s often because of too many requests, is what I should have said
