this post was submitted on 16 Dec 2025
24 points (96.2% liked)

Thunder App

3841 readers
1 users here now

An open-source, cross-platform Lemmy client for iOS and Android.

This community is intended to discuss features and feature suggestions for Thunder; as well as friendly, respectful talks about Lemmy in general.

Please use the GitHub repository linked below to submit bug reports, so keeping track of them is easier, and make sure to search first if you already can find an issue for your report.

If there are any developers who would like to contribute, feel free to reach out on GitHub!

General Links
Website: Link
GitHub Repository: Link
Matrix Space: Link

Android Releases
IzzyOnDroid: Link
Google Play: Link

iOS Releases
Apple App Store: Link
TestFlight Beta: Link

Related Communities
Nightly Community: Link

founded 2 years ago
MODERATORS
darklightxi@lemmy.world
poolitzer@lemmy.world
darklightxi@lemmy.ca
micahmo@programming.dev
micahmo@lemmy.world
24
Constant "Instance of LemmyApiException" on every scroll, even the tiniest amount (thelemmy.club)
submitted 1 week ago* (last edited 1 week ago) by Quibblekrust@thelemmy.club to c/thunder_app@lemmy.world
10 comments fedilink hide all child comments
 

Version v0.8.1. Android 16. Pixel 7 Pro.

After scrolling a couple pages (endless scrolling is on) I start seeing "Instance of 'LemmyApiException'". Once it starts, the tiniest amount of scrolling—even upwards—causes the error. I can make a bunch of rapid, itty bitty scrolls, and each one will hide and reshow the error.

What is Thunder doing with the API on every single scroll? Even up? Makes no sense.

I don't have "mark read on scroll" enabled, or anything odd. I haven't changed any settings in weeks, and this started happening just a few days ago. It might only be happening on my home instance. I could test with an alt.

Update: I can't reproduce this using a lemmy.world account

top 10 comments
sorted by: hot top controversial new old
[–] darklightxi@lemmy.world 2 points 4 days ago (2 children)

Just wanted to provide some updates - v0.8.2 is now released which should resolve this issue. Please let me know if you continue to see this after updating Thunder!

[–] heydo@lemmy.world 1 points 3 days ago (1 children)

I am on v0.8.2 on and I am seeing this error message whenever I try to go to my All feed. It won't load and I see this error message. And then it loads up my Subscription feed.

[–] darklightxi@lemmy.world 1 points 3 days ago (1 children)

Hey there, could I get more details on this? For example, the instance you're having issues with, whether you're logged in or not, any reproducible steps, etc.)

[–] heydo@lemmy.world 1 points 2 days ago* (last edited 2 days ago) (1 children)

EDIT: I was wrong, the issue is still occurring. If I have the "Show Read Posts" option unselected, then this error message appears. If I select that, then my All Feed will load ( but it has all of the posts I have read loaded on the screen). I forgot that I had made that change and that is what made it work.

Sorry, it's lemmy.world and I am logged in. The issue isn't occurring anymore though, nothing was changed so I don't know what happened.

It was basically just whenever I tried to view my All feed it wouldn't load it and gave me the same error message as in OP's picture. But since it is working now and I can't reproduce it, I guess there's nothing that can be done.

[–] darklightxi@lemmy.world 2 points 2 days ago

Thanks for the information! I'm able to reproduce the issue on my end with the details you provided. I'll try to get a fix out for this soon once I investigate it further.

[–] Quibblekrust@thelemmy.club 2 points 4 days ago

Awesome, thank you for the quick turnaround! This has been a app-breaking issue. Actually, it's been great. I could only scroll through the first 100 posts, and then I have to go do something else. 😂

[–] Switorik@lemmy.zip 4 points 6 days ago

I'm experiencing the same problem.

[–] TIN@feddit.uk 7 points 1 week ago

I've been getting the same

[–] darklightxi@lemmy.world 5 points 1 week ago

Hey there, thanks for the heads up!

This seems to be a recent issue caused by Lemmy v0.19.14. It's likely that your home instance updated to that version which is causing issues with client apps using page to fetch items. See here for more details: https://github.com/LemmyNet/lemmy/pull/6252

See this other post which has more relevant information: https://lemmy.ml/post/40358485

[–] Alexstarfire@lemmy.world 4 points 1 week ago