32 Could not authenticate you

[dr-codswallop]

Hi there,

Not sure if a plugin issue or Twitter auth itself, but all of a sudden I'm now receiving "32Could not authenticate you" on all local & production sites I have your plugin installed on. CP admin shows wording "something wrong" on the access token screens on all sites.

In light of this, could I suggest improving the error handling for at least the Twig output. The "32Could not authenticate you" message isn't ideal for live sites.

Maybe leave a blank output if .env is set to production?

[pixelman]

Hello, we have the same issue with the plugin.
We are still using craft v3.x, so we are using version 1.0.8 of the plugin.

Updating craft is currently not an option as we are working towards an upcoming event. And our registrations are running.
Any suggestion what this problem could be?

In the settings of the plugin we also get an error (something wrong) for creating the tokens.

[dr-codswallop]

Correct me if I'm wrong but I believe this is due to Twitter recently enforcing paid access to use their API to fetch tweets. Free access is limited to only posting, wheras $100/month gets you read access to 10k Tweets. Ouch!

https://developer.twitter.com/en/docs/twitter-api

Seems like the end for this plugin 😢