EsaDev

nfc.py error output

Jul 7th, 2020
77
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 1.81 KB | None | 0 0
  1. ERROR:spotipy.client:HTTP Error for PUT to https://api.spotify.com/v1/me/player/play?device_id=my_device_id_here returned 400 due to Invalid context uri
  2. Traceback (most recent call last):
  3. File "path_to\Python\Python38-32\lib\site-packages\spotipy\client.py", line 175, in _internal_call
  4. response.raise_for_status()
  5. File "path_to\AppData\Local\Programs\Python\Python38-32\lib\site-packages\requests\models.py", line 941, in raise_for_status
  6. raise HTTPError(http_error_msg, response=self)
  7. requests.exceptions.HTTPError: 400 Client Error: Bad Request for url: https://api.spotify.com/v1/me/player/play?device_id=my_device_id_here
  8.  
  9. During handling of the above exception, another exception occurred:
  10.  
  11. Traceback (most recent call last):
  12. File "C:\Users\esama\AppData\Local\Programs\Python\Python38-32\lib\runpy.py", line 193, in _run_module_as_main
  13. return _run_code(code, main_globals, None,
  14. File "C:\Users\esama\AppData\Local\Programs\Python\Python38-32\lib\runpy.py", line 86, in _run_code
  15. exec(code, run_globals)
  16. File "C:\Users\esama\Desktop\nfc\nfc.py", line 116, in <module>
  17. client.start_playback(device_id=spotify_device_id, context_uri=args.uri[0])
  18. File "C:\Users\esama\AppData\Local\Programs\Python\Python38-32\lib\site-packages\spotipy\client.py", line 1330, in start_playback
  19. return self._put(
  20. File "C:\Users\esama\AppData\Local\Programs\Python\Python38-32\lib\site-packages\spotipy\client.py", line 225, in _put
  21. return self._internal_call("PUT", url, payload, kwargs)
  22. File "C:\Users\esama\AppData\Local\Programs\Python\Python38-32\lib\site-packages\spotipy\client.py", line 186, in _internal_call
  23. raise SpotifyException(
  24. spotipy.exceptions.SpotifyException: http status: 400, code:-1 - https://api.spotify.com/v1/me/player/play?device_id=my_device_id_here:
  25. Invalid context uri
Add Comment
Please, Sign In to add comment