Community of the Android app Boost for Lemmy
This exact issue is happening to me. On every category, even Local. The first page loads instantly, the second and other pages timeout.
I am on lemmy.world with Boost. I have lots of muted communities and some things blocked but not much.
It has been happening for weeks on my side, it never worked since I have this issue (so it is not intermittent) and even as a Guest (lemmy.world) the problem occurs.
Feel free to ask questions. I would be glad to help ๐
Personally, I'm getting burnt out with lemmy. Every update creates more bugs and because the developers don't experience them, they don't get fixed.
Boost is still broke. I moved to thunder, the last update to thunder completely broke it but the developer isn't experiencing it so whatever.
Before this, I made two accounts and both of the instances stopped updating or closed causing complete loss of account.
Nothing works for more than a few months it seems.
I'm on a samsung s25 ultra, a current phone. It's not on my end.
I've been there but I think it's instance related. If your instance can't connect you to either itself or other instances you'll get a 503 error.
A fix, sadly, it's too wait until the admin of your instance fixes their connection problem. Usually it's unscheduled maintenance.
I'm not convinced. This started happening the moment the last update for boost released. It does it both locally and with other instances. It loads any instance/community fine.
I'm just sharing my experience. If it's an issue with the app itself, I think Ruben will keep an eye on it all and maybe you can contact him with some more details so he can debug properly.
I appreciate the info. I'm going to try another app and see if the same issue persists.
Edit: I tried sync and I do not experience this issue.
This happens to me only on the Subscribed / Home tab. Everything else does infinite scroll.
It's been happening for maybe 3+ months. I've stopped using Lemmy because of it. I keep hoping it gets fixed.
Came to this channel looking for other people having this issue, as I'm also experiencing the same symptoms. Individual channels load correctly as described in the post, but I only get the initial load of posts in subscribed when I open the app, and trying to switch to all results in a timeout.
Edit: clearing the cache did not resolve the issue, nor did logging out and logging back in.
I'm still experiencing this and apparently you're the only other one willing to post about it. It would be nice if boost was more active in development.
I think it's just the one person, right? Understandable. But more to the point, maybe it's a rarely occurring issue?
For reference and for anyone potentially finding this in the future, I'm running boost on a galaxy note 20 ultra, android 13. If more useful technical info, or if the app creates logs of some sort, I'd be happy to share those as well.
Sorry I missed this post. I will try to replicate the issue.
Let me know if I can help at all. I really appreciate you reaching out!
I experience the same issue as guest. I have tried uninstalling, deleting cache, clearing data, logging out/in. I do not experience the issue with similar apps. S25 ultra.
Could you give some steps to reproduce? Instance, feed and sort, and most important, the timeout error message. Thanks
Is there anyway to see a more descriptive error log? This is what pops up on the bottom of the feed.
The timeout message appears as soon as it tries to load any posts passed the initial refresh on both all and local instances. I've tried sorting by hot, new, most comments, and the various top sorting methods. The error does not appear if I sort by old.
Edit I would like to add that this error does not appear for individual communities. They have infinite scroll and the sorting methods work as intended.
This error is tied to the main all and local feed.
Sorry if it was already answered, but does it happen when browsing as guest too?
It was affecting me as guest, but when I closed the app and re opened it still as guest, the issue went away.
I swapped back to my account and the issue came back.
I can live with guest for now.
Do you mark many posts as read and have the "Show read posts" disabled? Are you blocking any instances?
I even registered an account on lemmy.zip and I wasn't able to reproduce it :(
I do not have show read posts disabled but I do block the NSFL communities as i don't want to see gore on my feed. I seen one other person on here with a Samsung that claims they have the same problem. I'm not sure what the others use.
I think it's related to the sorting algorithm (all, new, etc). Do you have any custom ones or settings for it? I'm not familiar with how those are coded, but I remember them having a major issue about two years ago.
I understand this issue affects a small group of people and I don't want you to waste development time. I do appreciate the work you're putting into this.
I would like to mention that I tried thunder, sync, and jerboa. Thunder and sync work as intended. I tried jerboa today and it has the same timeout error as I'm experiencing on boost.
I'm not sure what that means since it works on some apps but not all.
I'm having the same issue
rmayayo is looking into this, do you have any info to add to this? Feel free to reply to his comment on this thread. Thank you
One month later and the issue still persists.
Came back here to share that, for me, as of today, I'm no longer experiencing this issue. I'm able to scroll down my feed and have it load new posts, and I can once again access the 'all' feed. Unsure if the app updated automatically. I've done absolutely nothing to resolve the issue and made no changes to my account. No Android updates between my last post and now. Maybe it was a backend issue with the instance I'm on (feddit.nl)?
At any rate, wanted to share. Hopefully yours clears up similarly.
I'm glad it's working for you. I just checked and it's still broke.
Aw man, I'm sorry to hear that. If I can think of any other variables that may have changed between my last post and now I'll come back to mention it, but I really don't know what it could be. Didn't change any apps or anything (though who knows what updates may have been pushed automatically).