You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The issue is that Twitter itself gives you several different secret keys to choose from:
If you use the Access Token and Secret, you'll get a NilAssertionError, but no information that actually tells you that you're plugging OAuth2 keys in to an OAuth1 provider. In this case, you need to use the "Consumer Keys".
I'm not really sure what the actionable item is here, but here's a few options:
Upgrade Twitter to OAuth 2
Add docs telling you which one of these to use (i.e. the Consumer Keys)
Rescue the nil assertion, and raise a better exception that tells you your keys are not valid OAuth1 credentials.
The text was updated successfully, but these errors were encountered:
The twitter auth is a bit tricky. All of the current supported engines use OAuth2 except Twitter.
multi_auth/src/multi_auth/providers/twitter.cr
Line 65 in 35ca2a6
The issue is that Twitter itself gives you several different secret keys to choose from:
If you use the
Access Token
andSecret
, you'll get aNilAssertionError
, but no information that actually tells you that you're plugging OAuth2 keys in to an OAuth1 provider. In this case, you need to use the "Consumer Keys".I'm not really sure what the actionable item is here, but here's a few options:
The text was updated successfully, but these errors were encountered: