unexepected keyword argument 'sp_dc'
See original GitHub issueI’ve followed the instructions and added the cookie values to my secrets and config.
Config:
…
spotcast:
sp_dc: !secret spotcast_client
sp_key: !secret spotcast_key
…
secrets.yml:
…
spotcast_client: asdf***asdf
spotcast_key: asdf***asdf
…
When using the dev tools to start a stream, I receive this error message:
Fehler beim Aufrufen des Service spotcast/start.
get_spotify_token() got an unexpected keyword argument 'sp_dc'
What am I missing? I’ve tried adding quotes to the values in secrets.yml. I’ve tried logging in again and receiving new tokens. That didn’t help. What else can I try?
Thank you for building this!
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:5 (2 by maintainers)
Top Results From Across the Web
cli download fails with unexpected keyword argument ... - GitHub
cli download fails with unexpected keyword argument ... Running the download in the python shell doesn't return any issues ✓ :.
Read more >unexpected keyword argument in simple Python code, why?
I'm trying to use the pymarc MARCReader library class. My python code is choking at the line: reader = MARCReader(file(input), ...
Read more >Error Message "Unexpected keyword argument passed to ...
After Keras is upgraded to 2.3.0 or later, the following error message is displayed:TypeError: Unexpected keyword argument passed to optimizer: ...
Read more >TypeError: __init__() got an unexpected keyword argument ...
After completing all the procedure, the following error was thrown while running run.py TypeError: init() got an unexpected keyword argument ...
Read more >init__() got an unexpected keyword argument 'values'
I am just beginner and trying to populate slots like in the image.getting the above error.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
It seems 3.2 has a problem. I’ll fix it tomorrow morning. In the meantime use the older version
Should be fixed in v3.2.1