Please report bugs using the following format in your title.
[
] Issue here
Hi again, your app is getting better and better on each release, thanks! Today I would like to report:
spoiler
It seems spoilers doesn’t work on Bean yet
A couple more fixes are incoming:
- 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
andscaleDownLargeImages
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.
The hacker theme looks so amazing. Thank you so much. Let me know if there is a link to donate. Would be more than happy to do so
Changelog August 2nd
Build 2023.08.02.01.29
- Added Toebean icon pack designed by my friend Noah (Instagram)
- Improved GIF -> JPEG representation rendering to only do it on animated GIFs.
- Fixed cut off text on Markdown lists.
- Fixed bookmarking.
- Added a loading indicator when navigating to a federated community.
- A toast is now show if a community cannot be loaded.
- Added a basic empty state to the inbox.
- Added the ability to block or unblock a community.
- Added a notice when a community is blocked and the ability to view it anyway.
- The image viewer can now be dismissed by swiping up.
- Added loading indicators for images.
- Fixed post title not showing on comments in the user profile.
Hi Steve,
A small [ BUG ] i want to bring to your notice, I’m still not able to see my bookmarks after reinstalling the app and I’m on the latest build,.
Otherwise the the app feels very snappy and polished already.
And I love the new set of icons too.
Thanks and appreciate your time and hard work on this.
Thank you! Out of interest, do you have Hide Read Posts on?
It’s OFF by default.
Yeah I know, I just haven’t been able to replicate it on my side and that’s the only thing I could think that might cause it.
deleted by creator
Changes: July 25th
build 2023.07.26.00.32
- Added the ability to create a post from community screens. This will be improved in upcoming builds with the ability to upload images and also select which community you wish to post to. Please test it in the meantime though.
- Switched to using the large title style for the nav bar and added an option to the Display settings toggle it off.
- Pulled out comments on user profiles.
- Added an option for Full Screen Swipe to Go Back to Actions settings.
- Added options to the Actions settings to hide floating action buttons.
- Added an option for the comment line width.
- Added an option to the Filtering settings to unbar NSFW images. For science.
- Fixed the incorrect background colour on the Search screen.
- Fixed some visual issues with the image gallery.
- Fixed visual issue with long community names.
- Fixed issue where sometimes the large title would not collapse correctly.
- Fixed an issue that could cause the wrong account to load on the Account tab.
- Fixed an issue that caused the count and vote not to show correctly on the single post view.
- Fixed an issue that allowed you to tap through to your own profile from your profile screen.
The overlay is a bit confusing at the bottom of a thread and it’s hard to reach the upvote on the left. [edit] bean is still my go to Lemmy client btw. Can’t wait for the upcoming releases. You’re a blast, Steve. Thanks a lot.
Thank you, I’m glad you’re enjoying Bean! It looks like this is a positioning but in themes with translucent tab and nav bars. I’ll look to fix it tomorrow but in the meantime if you use the Dusk theme it should solve it.
Changelog August 6th
Build 2023.08.06.22.41
- Added the ability to sort comments.
- Added a default comment sort to the Filtering settings.
- New theme: Midnight
- New theme: Forest
- New theme: Hacker
- New font: Futura
- New font: Menlo
- Fixed correct font styles not loading in the markdown editor.
- Fixed http:// and https:// links automatically being detected.
- Updated dependencies including SDWebImage. Should solve some crashing images with WebP and SVG parsing.
- Stopped reloading Inbox on focus as it seemed to be causing some glitches. Will reassess later.
–
Push notifications are now also functioning as expected. Please test and let me know if you encounter issues.
New themes, fonts, and comment sorting options added to Bean today 🥰
Great update! And I have a new favorite theme. I’ll probably be rocking Midnight for a little awhile.
That’s what I’m rocking too! Heavily inspired by the old Twitter theme that I will dearly miss 😭
I was going to say, it definitely reminds me of old school Twitter!
Same! I love midnight
Today’s big change (aside from earlier’s network rewrite) is image uploads and a redesigned post composer.
It’s going to be hitting TestFlight in a few minutes so please let me know what you think when you’ve had a chance to try it 😄
Tried testing the new image uploader with a cat photo on this reply. It says “uploading images” but nothing uploads.
14 Pro Max with iOS 16.6 btw.
Huh that’s weird. I wonder if that specific image is causing issues? Are you able to try another?
It worked from my lemmy.world account. Lemm.ee must not support images.
I should put a check in for that then. Cheers for the heads up!
The error it gives me when I use the mobile site is that my images are too large. I’m betting that it’s either a generic error because they don’t actually support images, or they have the limit set so low that it’s effectively disabled.
Maybe the best thing is to pass on any error messages the server gives the user trying to upload?
I’ve just pushed a build that will hopefully stop any slow down or crashes when scrolling. It still needs some optimisation but please let me know if you encounter any issues.
I love the toebean icons in this new build. You have one for each of my cats! So far so good with the scrolling too.
I need to see photos of the cats!
Also, please check out my very talented friend, Noah’s Instagram who I commissioned to design that set.
Ask and ye shall receive!
One more because the orange cat doesn’t look very orange in the first…
Aw, very cute!! They like grown up versions of my parents’ cats Harry and Daisy😄
Thanks. They are barely grown up. Xander (orange) is 1 and Xedo (tuxedo) is 1.5.
Digging the new icons as well. I’ll check out the artist’s insta!
Issues with opening communities within the community tab. No action happens when clicking on a community
I can’t duplicate this one on any of my accounts. Have you tried the old logging out and back in cliche?
Of course. Work-a-round is using the web browser and then adding and or pinning a community. Once it’s pinned it typically works in Bean.
Tap to collapse comments is no longer working for me.
D’oh! I undid the fix. Will sort today.
Some more feedback:
- search for comments would be nice
- 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)
- Searching comments is on my list.
- 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
Thanks :)
steve! loving the app so far man. couple questions -
-
will you be adding screen swipe to go forward at any point?
-
i’m having the same bug that another user mentioned where my saved/bookmarked posts aren’t showing up; it sounds like you aren’t able to reproduce this at this time but just wanted to give a heads up!
thanks again and looking forward to watching this all continue to grow!
I’d love to support swipe to go forward! It’s not massively high on the priority list at the moment though.
tested this out a bit more, i saved a new post inside of bean and this post did in fact show up in bookmarks. it looks like any previously saved posts are what’s not showing up. i believe the post i saved before was via memmy. going to test it out by saving a post on lemmy on desktop tomorrow and see if the same result happens!
edit: tested out by saving a new post on memmy and checking bean; that post is showing up on bean in bookmarks. weird quirk but i think the solution might just be for users to re-save previously bookmarked content if it’s not populating in bean
Huh, that’s so weird. They should be coming out from the API. Are they showing on the website okay?
i may have figured it out; the post in question that i’m not seeing in bean is this one - https://lemmy.world/post/401441
(i tried unsaving/saving from desktop as well as inside bean and am getting the same result)
the community this post is from is https://lemmy.world/c/kbinMeta@kbin.social - i wonder if that may have something to do with it? i also tried saving a different post from this community and was also unable to see it on bean
interested to hear your thoughts!
Ah it’s Kbin! It’s possible there’s an issue with the interop between Lemmy and Kbin via ActivityPub. I’ll see if there’s an outstanding issue for this on the Lemmy GitHub tomorrow.
awesome, sounds good man!
-
Seems like the line spacing is a bit out of whack, definitely not as condensed as it should be (especially obvious in comments).
Are you able to share some screenshots?
Sure. I’m not sure if I just dreamed it up or something, but I remember there being less space between lines.
Across the board it should be that line-height.
Oh really? Huh, I remember it being a bit more condensed…idk, maybe it was bugged for me earlier. Either way, thanks for checking in!
Oh also, some minor feedback: the color used for the ‘Reply’ swipe doesn’t really fit the rest of the app’s aesthetic imo. Then again, it’s just a matter of taste.
That’s a placeholder at the moment. I’m using the same colour as the “success” toast so it is a bit wonky haha.
Ah. Well, I’m glad there’s potentially a better color in the works lol
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.