I'm not too familiar with ways to handle this given the limitations (no client secret for example).
However, the issue is some resources redirect to authorization dance again. (i.e. to repeat login). But it's not always obvious when this would happen so we need a robust-ish solution.
I'm not too familiar with ways to handle this given the limitations (no client secret for example).
However, the issue is some resources redirect to authorization dance again. (i.e. to repeat login). But it's not always obvious when this would happen so we need a robust-ish solution.
I'm currently going to attempt using
requests.Session
response Event Hooks.