[BUG] - Refreshing token seems broken in some cases

[heysamtexas]

There is a case when the refresh_token flow is unable to re-acquire. I assume it is getting a a 401.

My hypothesis is that this is because I'm using the same app keys and secrets for my app with X.

Once I renew in my production app it will invalidate the tokens in dev, and vice-versa.

Therefore, you need to have two separate environments, which X (Twitter) now makes that difficult.

Either way, we should solve this problem below:

1. Once your refresh token is invalid you need to re-auth the whole thing anyway.

See stack trace:

2024-10-22 13:17:29,137 [DEBUG] Command.run_workflows (run_workflows.py:32): Publishing to access_token = OAuth2ProviderFactory.get_provider("twitter").get_valid_token(destination.oauth2_provider)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "oauth2_capture/services/oauth2.py", line 180, in get_valid_token
user_info=self.get_user_info(token_data["access_token"]),
~~~~~~~~~~^^^^^^^^^^^^^^^^
KeyError: 'access_token'