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
❯ docker run --rm -it \
-v .:/app/data \
ghcr.io/dmunozv04/isponsorblocktv \
--setup-cli
Could not load config file
Blank config file created
Welcome to the iSponsorBlockTV cli setup wizard
Paired with 0 Device(s). Add more? (y/n) y
Enter pairing code (found in Settings - Link with TV code): REDACTED
Pairing...
Paired device: YouTube on TV
Paired with 1 Device(s). Add more? (y/n) n
API key only needed for the channel whitelist function. Add it? (y/n) y
Get youtube apikey here: https://developers.google.com/youtube/registering_an_application
Enter your API key: REDACTED
Traceback (most recent call last):
File "/app/main.py", line 3, in <module>
helpers.app_start()
File "/app/iSponsorBlockTV/helpers.py", line 128, in app_start
config_setup.main(config, args.debug)
File "/app/iSponsorBlockTV/config_setup.py", line 59, in main
config["apikey"] = apikey
~~~~~~^^^^^^^^^^
TypeError: 'Config' object does not support item assignment
Expected behavior
No crash? 😅
iSponsorBlockTV server (please complete the following information):
OS: macOS 14.2 (arm64)
Apple TV (please complete the following information):
Hi there, thanks for reporting the issue. I've managed to fix it and will push a new version soon. In the meantime, you could manually edit the config.json file that will be created on the data_dir directory or use the TUI setup wizard, which shouldn't have this problem (replace --setup-cli with --setup on your docker run command
Describe the bug
When running the
docker run
command from the docs to generate a config, this happens:Expected behavior
No crash? 😅
iSponsorBlockTV server (please complete the following information):
Apple TV (please complete the following information):
4.19.75 #1 Thu Nov 2 10:49:42 JST 2023
BRAVIA_VH21_UC-user 10 QTG3.200305.006.S362 674801 release-keys
Screenshots
My Google Cloud console credentials page:
The text was updated successfully, but these errors were encountered: