The weird layout issue caused when tapping a username in the comments.
GIFs will no longer be automatically rendered as animated images anywhere in the app, except when opening the image viewer.
I want to give a bit more context about 2.
GIFs (and animated WebP images) have been the most common cause of crashes and UI freezes in Bean. The last couple of days have been particularly bad as this image of the Lemmy version of r/place has been shared.
This image is 12.4MB, animates for over 2 minutes, and (most importantly) is almost 3,000 frames. I can't even tell you exactly how many frames as both Preview and Photoshop froze on my Mac when trying to open the image.
The reason the number of frames is important, because a GIF is just a container for multiple images. Each frame is an individual image that needs to be decoded and rendered on the screen, and it turns out when there are a lot of them at 1000 x 1000px it is impossible to decode performantly.
Bean uses SDWebImage to download, cache, and render images behind the scenes. It's a fantastic library that is the de facto standard when working with remote images on iOS or macOS. Even with the progressiveLoad and scaleDownLargeImages options enabled, SDWebImage just cannot render certain images without iOS sounding the alarm and firing an OOM exception — especially when that image is 12.4MB and 3,000 frames.
At the moment, Bean will crash if you attempt to open this image. I have even tried working around this and rendering it in a web view, or using another library — FLAnimatedImage. Neither of these solutions worked and believe me, I'm not happy about that (seriously, I really hate GIFs now).
In the coming days, I'll be pushing another update that will check for the size of the image before deciding whether to animate it or not. When not animated, SDWebImage only decodes the first frame of a GIF which is no issue at all.
I know this isn't brilliant, as in the ideal world every image would be viewable within Bean, but it's the best solution I can think of to avoid a single image crashing the app.
At the moment the upvote/and downvote swipe colours match those on the buttons and does change for some themes. The reply colour does need attention as the bookmark one does use the accent.
I’ll give it some attention when I get 5 minutes or am working on new themes.
Since the last update, communities and comments haven’t been loading quite right. Always possible that it’s a .world problem, but I’m using Voyager right now without any apparent issue. I’ll try again in a couple hours and see if there are still issues.
Edit: I take it back. More exploring on Voyager reveals the same problems. Looks like it’s a .world issue.
I’ve pushed an update to the way images are rendered tonight which I’m hoping will finally (finally), finally (FINALLY) fix the crashing issues caused by GIFs and animated webp images exhausting memory allocation.
I have noticed that it’s broken the full height images option (sorry about that) so I’ll be patching that back in tomorrow.
In the meantime, I’d you encounter any issues with GIFs, please let me know.
Yeah my initial implementation was a hot mess. I’ve re-written my scheduler and worker so it should be more reliable. You’ll need to turn notifications off and back on again to re-register and hopefully that will fix it.
I think the splash screen should only be a skeleton of the tab bar/nav bar. The icon might not fit the user chosen app icon, also it makes the app feel slower. Apple’s HIG also recommends the skeleton
images in the feed should have the full height (otherwise most memes and posts aren’t readable without a tab and dismiss)
I know HIG recommends the skeleton but I’ll have the same issue where that splash might not match theme chosen by the user and that’s even more jarring.
There’s a setting for this under Display > Full Height Images
I'm having problems with the communities tab in the most recent release. Entries are sometimes getting duplicated or showing out of order, and I'm experiencing stuttering and slow loading. The app is slow to respond if I try to navigate away from the communities tab- sometimes taking several clicks or seconds to respond- while responsiveness in other tabs is normal. The battery usage has also been noticeably higher than before. I'm on an iPhone 11 pro, 16.5.1.
The duplication seemed to continue the longer I stayed in the tab and would cause jumping to other areas without any input on my part.
Duplicate entries are clickable links that lead to the correct communities.
The issue seems worse the more communities I'm subscribed to. I'll attach screenshots from the account with the most subscriptions, but other accounts show only one or two duplicates and my account with the fewest subscriptions didn't have any issues. I unsubscribed from a few on this account and am no longer seeing duplicate entries but am still experiencing the slow loading/high battery usage.
Unrelated but certain subscriptions are missing from the tab, notably !kbinMeta@kbin.social. This community shows up under my communities in other apps I'm testing, but not in Bean; maybe because the display name starts with a / and the other apps are sorting by the actual link?
Sure, I tried deleting and reinstalling and was not able to reproduce the duplication issue, though the slow loading/page jumping around/lack of responsiveness is still present.
Out of curiosity I tried subscribing to a new community and the bug reappeared, though not as bad this time:
I tried reinstalling again and the bug still persisted. I then unsubscribed from a community bringing my subscription count to 200 and that seems to have resolved the duplicate entries for now.
Running into a bug where images don’t load in the feed (seemingly random) but load fine when post is opened. This is one example of a post that showed a blank image icon until clicked
I know some instances like .world were having issues with thumbnail generation so this may be related. That being said, today’s build changes the way images are rendered in the background so please let me know if you see this frequently and I’ll investigate more.
Full height image preview seems to have stopped working in latest build. I’m seeing clipped images even with the option toggled on. Worked fine in previous build. This post is one example:
As for the other, I'll see what's being returned from the API. I wonder if the listing of posts returns something different to the single post endpoint.
I have the theme set to “automatic” but the app doesn’t switch from light mode or to dark mode unless it’s forced closed and re-opened. Most other apps seem to switch as soon as you open them, even if they haven’t been force closed and closed by iOS.
This looks like it uses the standard search API but allows you to define an instance you’d like to search. I think I could integrate a similar feature but I’d like to allow folks to explore other instances without having an account there too
Thank you! I’m aware of those bugs and I’ll add a compact comments view to the list. It is possible to turn off the footer there in the settings already.
Thanks :)
I saw that but turned them on again since there’s no other way to tell if a comment is upvoted or not (the upvote swipe doesn’t indicate on/off either)
And, not to bombard you, but there seems to be an issue with replies showing up. I know there are a few replies to my comment shown in the image, but they’re not appearing in Bean. It seems to be a problem in posts with a lot of comments, at least as far as I can tell.
It seems none of the links at Trending Communities are working for me. Do you know if it’s an issue with how they do their links, or something that can be adjusted on Bean?