Love the app, thank you for the continued development and being so in touch with the community ♥️
this post was submitted on 20 Dec 2025
72 points (100.0% liked)
Summit
1201 readers
21 users here now
Community to discuss Summit, an open-source Lemmy reader for Android.
App (Play Store): https://play.google.com/store/apps/details?id=com.idunnololz.summit
APK: https://github.com/idunnololz/summit-for-lemmy/releases
Source: https://github.com/idunnololz/summit
Support the app
Website: https://summit.idunnololz.com/
founded 2 years ago
MODERATORS
Thank you for your work, enjoy the holidays!
Thank you! You too!
Thanks!
I'm still getting some missing images, the 500 error I think?, and eventually the 400 bad request error after scrolling way down my feed.
500 errors are typically not caused by the client but instead indicate a server issue. Also, the new update only changes the default user agent. If you have changed the user agent manually via Misc > User agent in settings then this update will not change anything. You can try out changing the user agent yourself to a different one to see if it fixes the issue.
I have user agent set to let the app decide.
I installed bloorp a few days ago and started using it. I'm comparing it and summit. The 400 and 500 error images simply don't show anything in bloorp, whereas summit shows the error, so yeah, not an app issue.
However, there are several images that load in bloorp and not summit, which gives an unknown error, getPixels failed with error invalid input.
There is also the feed ending and not showing additional posts in summit with the 400 bad request still while I can infinitely doomscroll in bloorp. Occasionally, though not often, clicking retry will load an additional page of results.
Edit: I tested all the user agents and none fixed the issue.
Looks like on lemmy.zip for some reason requesting anything above page 10 results in a "couldnt_get_posts" error however this doesn't occur on any other instance I've tested. The reason why other apps and web isn't affected is because they use cursor based pagination, instead of page index. The reason why Summit doesn't do this is because some features are simply easier using an index and also because Lemmy is very inconsistent about pagination. Some things are parginated with page indexes only so page indexes is the common ground for all pagination. Since Summit uses the same code for all pagination, not just posts (eg. for saved posts, search results, etc) it was simply easier to write it once using page index and not have to write two versions.
I can look into write a 2nd version that uses cursors in the new year as unfortunately it is a pretty big change and I should be taking a break at the moment.
Just FYI the 10 page limit is an issue with lemmy 0.19.4.
https://github.com/LemmyNet/lemmy/pull/6252
Some instances will have deployed their own fixes but most instances on this version will have this big/change
Huh. I must have gotten lucky when I checked since all of the instances I tried didnt have an issue. I tried lemmy.ml, lemmy.world and lemmy.ca.
.ml is on .15 beta, .ca is on .13 still, and .world have a custom patch in place ☺️
Does look like you'll have to update the method based on the comments on github though (not that I understand it all that well)
Interesting. I was able to reproduce this but only on your instance. I can take a look later today.
Getting missing images on a lot of posts, which show up fine on my normal instance in a browser (posting on an alt because I normally block lemmy.world)
getPixels failed with error invalid input
App otherwise still working great! Enjoy your break
Can you check Settings > Misc > Client user-agent and make sure " Let the app decide" is selected? If that is selected and you are still getting errors can you try playing around with that setting? If you find a certain setting works please let me know which one so I can figure out a better user agent to use. Thank you.
I'm pretty sure that this is a rendering error. Here's two screenshots:
In this first one, I tapped on the post thumbnail to expand it. Not shown: The first time I expand the post it'll show the image, and then replace it with the error after a fraction of a second.
The second image is from when I long press the thumbnail. It shows the image, but with the error overlaid.
Another updates on this. This image file is really weird. I downloaded the image and tried using a few other apps to few the image and non of them could load the file. I'm not sure if this is a bug with Summit or the file at this point since I downloaded the file using my browser and not Summit. Chrome was able to show the image but nothing else. I will dig deeper later today.
Update: the image loads on desktop. It looks like the built in AVIF decoder on Android doesn't support the set of features used in this image. This is problematic because a standalone AVIF decoder is larger than the size of the app so the app size would double if I were to use a standalone AVIF decoder. Hopefully this can be fixed on the server side so I wont have to greatly increase the app size.
Thanks for the update! I agree, this sounds like a server problem then.
Are you on Android 11 or below? It looks like a lot of instances have begun showing images in AVIF format. Unfortunately this file format is not supported by Android 11 and below. I wonder if this is what is causing a lot of these issues.
14, which still receives updates. Could it be a file size issue?
It seems unlikely. The reason why you still see the image is because posts typically have 2 images, a thumbnail (low resolution) and the source image (high resolution). When you tapped the post. You are first shown the thumbnail while the source images loads. This is why it looks like the images loads at first. In the full screen viewer the same thing happens. You are shown the thumbnail but the erro indicates that the source image failed to load. If you tap the "error details" button it should give you more information about the underlying cause.
I tried all the different user-agents, but unfortunately none worked. FWIW, although all images load on my browser on my main instance (lemmy.zip), and many fail in the app, switching to this lemmy.world account caused the image from the same post to load in the app without issue (using the flutter user-agent)
I'm still getting numerous of these unknown errors getpixel errors for images that load fine on the web and in bloorp. I played with the different client agents and nothing worked.
It's likely bloorp bundled a standalone AVIF decoder which is why it loads there. It looks like the AVIF decoder bundled with Android is unable to decode the AVIF image as evident by the fact that 3/3 image viewers I tried failed to load the image (4 if you include Summit).
Happy holidays 'lolz! Thank you for your wonderful app :)
Thanky you! Happy holidays to you as well!
I'm new to summit and it's great! This version fixed all the 401 responses i sometimes had when trying to open pictures.
Nice. Good to hear!