Hey everyone! This is just a small update that resolves some issues with Thunder v0.8.1 and Lemmy v0.19.14. As always, if you encounter any issues or have feedback, please share them with the Thunder community or on GitHub.
If you’re enjoying Thunder and would like to show some support, star this project on GitHub! This helps gain visibility for the project and allows more contributors to help with the continued development of Thunder. If you’d like to show some appreciation, here is a post with details on how to donate to the active contributors of Thunder.
We have a Matrix space if you would like to join in on discussions: https://matrix.to/#/#thunderapp:matrix.org
Additions
- Added ability to hide bottom navigation bar on scroll by hjiangsu in #1983
- Added support for .avif image formats by hjiangsu in #1996
- Added support for Lemmy page cursor in feeds by hjiangsu in #1997
Changes
- Improved background notification logic and checks by hjiangsu in #1990 and #1994
Fixes
- Fixed settings search elevation by micahmo in #1977
- Fixed transparent colour option being available as an app theme by hjiangsu in #1979
- Fixed inbox mark as read not updating UI correctly by hjiangsu in #1981
- Fixed max password limit for PieFed by hjiangsu in #1995
Misc
- Upgraded Thunder to Flutter 3.38 by hjiangsu in #1989
- Added PieFed instances to GitHub workflows by hjiangsu in #1972
- Updated instances by github-actions in #1920
- Updated translations from Weblate by hjiangsu in #1982
Thanks for all your work! Definitely the best Lemmy app I’ve used.
I’m getting a similar error as before, regarding scrolling. I got to a point where every scroll event is causing this to appear.
I’ll see if I can reproduce it, and what the steps are.
Update: It’s the same behavior as last time. I can load about 100 posts, and then I start seeing this error on every scroll, and no more posts get loaded.
Hey there! I haven’t had time to post a proper update yet, but I had to roll back the fix for this. It turns out the fix was causing some users to be unable to load the All/Local feeds at all.
This ended up being a bit of a catch-22 situation: I could keep the fix and completely break feeds for some users, or revert it and limit affected instances (running Lemmy v0.19.14) to about ~100 posts.
For now, here are a couple of ways to work around this issue:
Alright. Thanks for the update!