Closed detrout closed 5 years ago
There is a validation function, however it has not been released yet to a tagged version.
I fixed it by deleting the file. It was just annoying to find that so I wanted to leave a bug report to make easier for the next person it happens to. Thanks for letting me know there's a fix.
Fix is now in the latest release.
gplaycli
(should be 3+) Python 3.6.4 (default, Jan 5 2018, 02:13:53) [GCC 7.2.0] on linuxgplaycli -v
[INFO] GPlayCli version 3.24 [Python3.6.4] [INFO] Configuration file is gplaycli.conf [INFO] Using cached token.(it's actually direct from git, so the HEAD commit is c5920db9c1df43d09d7f97f2a05d26a41443e294)
gplaycli
:git clone
,git clone and setup.py
,pip install gplaycli
,apt install gplaycli
, ...mkvirtualenv --python=/usr/bin/python3 git clone, python setup.py develop
Somehow I got unlucky and the contents of the tokencachefile was "Malformed Request".
I'm not sure how the Malformed Request got there, but it might be nice to have some kind of validation function in gplaycli.py::get_cached_token that gives an error message if the contents of the token cache is invalid.
Once I figured out that the cache file had bad data in it, I deleted ~/.cache/gplaycli/token and gplaycli downloaded a new valid token