Prompt to reset the Meetup API authentication tokens, as we can't do it automatically. #317
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
At some point in the past while debugging a Meetup API issue, I was forced to change how the authentication reset process works, I'm unsure what the issue was, but it likely pre-dated the files being canonicalised here.
Recently (likely after the meetup.com password was changed) the events api ceased to import meetup events, throwing the following warning:
It seems like running the request with these changes, and re-authenticating the oAuth applications has restored the meetup.com ingestion.
The changes in this PR have been sitting in my development environment since ~May 2022, so I don't recall the exact reasoning behind it, other than it was likely to resolve this same error.
It looks like the main thing is that it attempts to check the
refresh_token
is valid and errors out if not, where as currently it seems to assume that the refresh_token will never be invalid. I think.This is a PR for now as I wanted to get the code off my hands and somewhere for others; I haven't fully tested and reviewed these changes to verify it does exactly what I think it does