You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is an approximative 10 seconds extra-wait on each entry finishing by 42 or 92. (142,192, 242...)
In global I think the general feed loading is between 50% and 60% slower than before because of this annoying bug.
Screenshots/Screen recordings
Screenrecorder-2024-11-27-21-11-49-34.mp4
Logs
No response
Affected Android/Custom ROM version
Android 15
Affected device model
Xiaomi mi 11
Additional information
No response
The text was updated successfully, but these errors were encountered:
ShareASmile
added
duplicate
Issue or discussion is a duplicate of an existing issue or discussion
and removed
bug
Issue is related to a bug
needs triage
Issue is not yet ready for PR authors to take up
labels
Nov 29, 2024
@JohnLemonade35 Sorry for the confusion due to my above comment, matters got mixed up 😀. it wasn't meant for you. I will take back my above comment.
Regarding feed loading is slower than before, We are forced to throttle feed loading due to rate limiting issues by YouTube see #11661.
However currently, loading screen blocks users from watching feed items etc while new items are being fetched. This behavior should be changed and there is an issue #4952 open for it. You can make suggestions there.
Checklist
Affected version
0.27.3
Steps to reproduce the bug
Just reload a feed and see.
Expected behavior
Loading all feed entries fast enough.
Actual behavior
There is an approximative 10 seconds extra-wait on each entry finishing by 42 or 92. (142,192, 242...)
In global I think the general feed loading is between 50% and 60% slower than before because of this annoying bug.
Screenshots/Screen recordings
Screenrecorder-2024-11-27-21-11-49-34.mp4
Logs
No response
Affected Android/Custom ROM version
Android 15
Affected device model
Xiaomi mi 11
Additional information
No response
The text was updated successfully, but these errors were encountered: