-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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] Visit any channel page: Unexpected token '' at line 1, column 1 #1838
Comments
Seems to be related to a YouTube API change: related YouTube-DL issue (comment includes a potential solution too) |
It's a pretty simple change since it's just a JSON wrapper that passes the same continuation/ctoken. I implemented it in my Python project here |
Selecting this issue for this bug since it has the most activity and information about the bug and potential solution. All further bug reports should be commented here, and new issues reporting it should be closed as a duplicate of this. To other contributors: please check if the labels are correct. |
Title: Backtrace
|
I am getting (a lot of) messages of the following type
Is this the same issue ? (figured ill ask before making a bug report of my own) |
This comment has been minimized.
This comment has been minimized.
Aside from not being able to visit channel pages, I also can't subscribe to channels:
Importing subscriptions doesn't work either, invidious will just return to subscription manager with 0 subscriptions after hitting "Import". |
Another example, it worked some days ago:
Commit id 9687d43 |
Nearly same line of text (header is same exc time) I get too at yewtu.be. At invidious.tube, there is different version [Version: |
This happens on every invidious instance I go on. |
Same issue on my private instance... when trying to view any youtube channel. Title: Backtrace
|
A new bug report. Do new ones provide any more useful information? Title: Backtrace
|
pull request 1849 has a workaround. Assuming you are building from master, heres what i did, it fixed the problem for my instance:
|
Yewtu.be seems to have been fixed |
Indeed, I've deployed the code from the pull request #1849. |
Is there a fix for a Docker-based setup?
Mar 5, 2021 11:39:35 schleussinger <notifications@github.com>:
… pull request 1849 has a workaround.
Assuming you are building from master, heres what i did, it fixed the problem for my instance:
sudo -i -u invidious
cd invidious
git fetch origin pull/1849/head:channelfix
git checkout channelfix
shards update && shards install
crystal build src/invidious.cr --release
exit
sudo systemctl restart invidious.service
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub[#1838 (comment)], or unsubscribe[https://github.com/notifications/unsubscribe-auth/AQPEB75IBOY5V53W45I2DSTTCCYGFANCNFSM4YQDSE6A].
[data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAFEAAABRCAYAAACqj0o2AAAAAXNSR0IArs4c6QAAAARzQklUCAgICHwIZIgAAAAwSURBVHic7cExAQAAAMKg9U/tYwygAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAOAGZtUAAZwPT44AAAAASUVORK5CYII=###24x24:true###][Tracking image][https://github.com/notifications/beacon/AQPEB726JAGG3RWKU5JM7E3TCCYGFA5CNFSM4YQDSE6KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOF4VNEGY.gif]
|
I don't know when exactly it started, but I've been having the same problem for a few days now (on Chrome OS if that matters).. I use primarily the snopyta domain, so I didn't know if anybody was having the same issue or if it was just me, or maybe just a problem with that domain. |
Hello, thanks a lot. Can you give me a pointer, how I can actually use
this? I basically just cloned the repo and did docker-compose up -d :-D
|
tle: Backtrace
|
can confirm, yewtu.be is still working on my end |
@TheFrenchGhosty this issue can be closed I guess now that #1849 got merged. |
Release it :D |
This issue has been automatically locked since there has not been any activity in it in the last 30 days. If this is still applicable to the current version of Invidious feel free to open a new issue. |
Describe the bug
Unexpected token (seems to be nonexistent JSON when it's expecting JSON data?) upon visiting any channel page. Tried with multiple channels and on multiple instances.
Steps to Reproduce
Logs (from yewtu.be instance)
Title:
unexpected token '' at line 1, column 1 (JSON::ParseException)
Date:
2021-03-03T02:01:38Z
Route:
/channel/UC-SV8-bUJfXjrRMnp7F8Wzw
Version:
2021.03.02-3af4207 @ master
Backtrace
The text was updated successfully, but these errors were encountered: