-
Notifications
You must be signed in to change notification settings - Fork 479
composer require socialiteproviders/twitter SocialiteProviders\Twitter\Provider does not extend Laravel\Socialite\Two\AbstractProvider #1193
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
My AppServiceProvider.php : public function boot(): void
{
Event::listen(function (\SocialiteProviders\Manager\SocialiteWasCalled $event) {
$event->extendSocialite('discord', \SocialiteProviders\Discord\Provider::class);
$event->extendSocialite('twitter', \SocialiteProviders\Twitter\Provider::class);
});
} |
Our twitter provider is a oauth v1 provider, which i'm guessing is why it's giving an error. |
Is there a reason why you can't use the offical socialite provider? |
Hi @atymic, sorry for the delay in replying, I hadn't seen your answer ! Here is my stacktrace https://flareapp.io/share/dPbD43A5 |
@atymic I might have figured out a solution. Can you please look at a closely related discussion I created? |
I am facing the same https://prnt.sc/7BCKbYMgx7PC Can anyone guide me |
I had the same issue, but with Discogs OAuth. Apparently, Discogs uses OAuth 1, and as @boradatti mentioned in the linked discussion thread, AppServiceProvider.php public function boot(): void
{
Event::listen(function (\SocialiteProviders\Manager\SocialiteWasCalled $event) {
$event->extendSocialite('discogs', \SocialiteProviders\Discogs\Provider::class, \SocialiteProviders\Discogs\Server::class);
});
} |
Any news about this issue? 🙄 |
+1 |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Well, same issue hre now in June 2025 :) P.S. @atymic
I assumed For whoever looks for a clue to fix that, the topic from @boradatti here and the comment from @andreas-bylund were very helpful to get the direction. Much appreciated for the only useful answers in the thread 😸 A quick summary:
This will at least make requests through with OAuth1-compatible communication. I am now struggling to get local domain (just "localhost" or local domains .local, .test, etc) - getting 401 Unauthorised from Twitter, guess I will try later on a real domain. But hey, that's the progress :) |
Fix for compatibility issues with the latest socialite plugin and eliminating error "SocialiteProviders\Twitter\Provider does not extend Laravel\Socialite\Two\AbstractProvider" Related topic for this issue and main discussion thread: SocialiteProviders#1193
当我使用twitter提供者会提示出错
The text was updated successfully, but these errors were encountered: