Bean 1.0.2 Release Notes
Bean 1.0.2 Release Notes
v1.0.2 rolling out to the App Store now.
- Added a setting to mark posts as read when scrolling past them.
- Read posts are now only hidden on refresh to stop the screen jumping.
- Truncated the text in link preview cards to 200 characters.
- Fixed multiple spoiler tags collapsing into a single tag.
- Fixed marking posts as read when viewing an image.
- Fixed image gallery not always appearing on post view.
- Fixed positioning of community selector and + button on the composer on some devices.
- Fixed pull to refresh indicator missing after first use.
- Renamed Harry icon to Xander.
Harry -> Xander. Is there a story or tribute there?
2 0 Reply@infinite_zero@sh.itjust.works requested it be renamed to honour their cat 😊
3 0 ReplyWell now I’ve gotta pay the Cat Tax…
3 0 Reply
Thank you for your continued work on the app.
2 0 ReplyI am hitting a few crashes on 1.0.2.
The main All timeline crashed killing the app. Now when I open it All is empty.
If I switch to another list (Local for example) it seems to work. But as soon as I switch back to All and try to refresh the timeline it crashes the app again.
This is using Feddit.uk
1 0 ReplyCan you try disabling the read posts and see if this still occurs?
1 0 ReplyI've logged into feddit.uk and can't seem to replicate this. Are you able to let me know:
- iOS version
- Which view you're using e.g. Compact/Card/Headline
- Any other settings you may have turned on/off
1 0 Reply
Brilliant update.
Thanks for the mark read in scroll. Going to give that a go now. It was my last major missing feature.
1 0 ReplyLet me know if you encounter any issues with it
1 0 ReplyWorking well so far.
The only obvious issue so far is that there no obvious way to hide read posts when in a community directly.
The ellipse is only available on the main timeline.
Another post suggested a hide/show read posts button. That would be a great addition, especially if it can be made optional.
1 0 Reply
Marking read on scroll doesn’t appear to be working for me.
1 0 ReplyCan you let me know if this persists in 1.0.3
2 0 ReplyThat’s fixed it! 👍
1 0 Reply