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
Make it similar to the error when loading a YouTube channel(s) but could not load any videos on it.
It shows the YouTube Channel(s) on top with the text: could not load from the following channel(s) but instead could not fetch/load subscription videos due to RSS failed to load
At the moment I have already reset my router and have gotten new IP, so I won't be able to check the fix(when it is available) and check if the issue still persist with the RSS not loading and still retaining the subscription cache
Nightly Build
I have encountered this bug in the latest nightly build.
The text was updated successfully, but these errors were encountered:
#5756 should solve this one but we have no way of knowing as the RSS is up again. Ill close this one but feel free to reach out when RSS is down and that PR didnt fully solve it.
Guidelines
Describe the bug
Expected Behavior
After refreshing the subscription video list, if it fails due to IP block by Google it should still be able to see the cache video list
Issue Labels
content not loading
FreeTube Version
9ca2c74
Operating System Version
windows 11
Installation Method
.exe
Primary API used
Local API
Last Known Working FreeTube Version (If Any)
No response
Additional Information
This bug report is in tandem with #5749
Make it similar to the error when loading a YouTube channel(s) but could not load any videos on it.
It shows the YouTube Channel(s) on top with the text:
could not load from the following channel(s)
but insteadcould not fetch/load subscription videos due to RSS failed to load
At the moment I have already reset my router and have gotten new IP, so I won't be able to check the fix(when it is available) and check if the issue still persist with the RSS not loading and still retaining the subscription cache
Nightly Build
The text was updated successfully, but these errors were encountered: