Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: Certain channels fail to load additional videos using local (and invidious) API #2901

Closed
5 tasks done
Kazcade opened this issue Nov 29, 2022 · 8 comments · Fixed by #3143
Closed
5 tasks done
Labels
B: API issue bug Something isn't working

Comments

@Kazcade
Copy link

Kazcade commented Nov 29, 2022

Guidelines

  • I have encountered this bug in the latest release of FreeTube.
  • I have searched the issue tracker for open and closed issues that are similar to the bug report I want to file, without success.
  • I have searched the documentation for information that matches the description of the bug I want to file, without success.
  • This issue contains only one bug.

Describe the bug

  1. Go to one of the channels in question. Some examples:

https://www.youtube.com/@Evolgam
https://www.youtube.com/@HandToolRescue
https://www.youtube.com/@hbomberguy

  1. Click on "fetch more results"
  2. encounter error "Local API Error (Click to copy): TypeError: Cannot read properties of null (reading '1')"
  3. no additonal videos load
  4. using invidious, only duplicates of videos load (see [Bug]: Fetch more results inside channel page results in current list of videos duplicating #2851)

Expected Behavior

Clicking on ""fetch more results" should load additional videos, not result in an error.

Issue Labels

API issue

FreeTube Version

v0.18.0 Beta, also latest nightly

Operating System Version

Windows 7 64-bit

Installation Method

.zip

Primary API used

Local API

Last Known Working FreeTube Version (If Any)

No response

Additional Information

No response

Nightly Build

@Kazcade Kazcade added the bug Something isn't working label Nov 29, 2022
@2HappyNerds
Copy link

2HappyNerds commented Dec 8, 2022

Linux has this issue. Sometimes tempoarily fixed by changing "Current Invidious Instance" setting and/or "preferred api backend" and/or "Proxy Videos Through Invidious". Error fetching videos, seems to affect certain specific channels ONLY! For me, this has only been since upgrade to v0.18.0 Beta.
some affected channels:

Navajo Grandma

WhispersRed ASMR
The French Whisperer ASMR
ASMRrequests

(approx 1:30 pm EST (us)
8dec2022)
Don't recall which invidious instance had error (vid.puffyan.us perhaps?)
switched to:
https://inv.riverside.rocks
it worked ...
now i was able to "Fetch more results"
...
whoops spoke too soon...
giving the oh-so-informative error message:
"Local API Error (click to copy): TypeError: Cannot read properties of null (reading "1")"
also fyi...
"click to copy" does not copy error message to clipboard...

that is the quickest i have had it go from working to non-working... noting date/time may help shed some light on what is causing this.

/***************************************/
this is what i had when working:
https://inv.riverside.rocks/
2022.11.22-5160d8ba

it is also what showed as the default instance... when it stopped working...

i closed, then re-opened freetube...

default instance had changed to:
https://invidious.sethforprivacy.com
2022.11.22-5160d8b

version info from:
https://api.invidious.io/?sort_by=version

//
am going to test different settings
as time permits
and make notes in add'l comment
/
/

right now i think it is important to note:
went from ErrorFetchingVideoList to Fetching add'l videos with No Errors
NO SETTING CHANGES on my part.
+No discernable difference in version of Invidious Instance Used
...

I will make more detailed notations for
VariousSettings

  • Invidious Instance Used
  • Version of Invidious Instance
  • Date/Time
  • ChannelsFetchAttempt-xx-Success
  • ChannelsFetchAttempt-xx-Error

Also need to append attempt number to ChannelsFetchAttempt denoting multiple fetches on same channel when it fails on 3rd attempt after having previously succeeding...


New Wrinkle I've noticed:
It sometimes begins failing when fetching multiple times. -- hence will include a number to ChannelsFetchAttempt as well as Success or Error


May experience this other known bug when fiddling with settings:
[Bug]: Fetch more results inside channel page results in current list of videos duplicating
#2851

@2HappyNerds
Copy link

2HappyNerds commented Dec 8, 2022

This is what I plan to record info about when
I next experience this issue:

Date/Time of "Test" Begin
CurrentInvidiousInstance
VersionofInvidiousInstance
ChannelName [ChannelsFetchAttempt-xx-Success]
ChannelName [ChannelsFetchAttempt-xx-Error]
Date/Time of "Test" End

Documenting Settings:

General Settings

Check for Updates [Selected]
Check for Latest Blog Posts [Selected]
Fallback to Non-Preferred Backend on Failure [Selected]
Enable Search Suggestions [Selected]

Preferred API Backend[Local API]

Current Invidious Instance [https://invidious.sethforprivacy.com]

Player Settings

Proxy Videos Through Invidious [Selected]
...

[Recording settings when working may help someone else know what to tweak]

source of my invidious instance version from:
https://api.invidious.io/?sort_by=version
at time of testing

@l3ale
Copy link

l3ale commented Dec 30, 2022

Same here, Win10 x64, v0.18.0 Beta .ZIP install.

Console stores the following error:

Capture2

@Kazcade
Copy link
Author

Kazcade commented Jan 14, 2023

I would like to update this with the information that the issue still persists in the latest nightly (2534). I would appreaciate it if this could be fixed, as it makes a number of channels unusuable.

@github-actions
Copy link
Contributor

This issue is stale because it has been open 28 days with no activity. Remove stale label or comment or this will be closed in 7 days.

@Kazcade
Copy link
Author

Kazcade commented Feb 15, 2023

Again, this issue still persists and any help in solving it would be appreciated.

@Masacroso
Copy link

Indeed this annoying error persists and affect many channels.

@efb4f5ff-1298-471a-8973-3d47447115dc

@Masacroso this is fixed in the latest nightly build.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
B: API issue bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants