Replies: 4 comments
-
|
I'm having the same issue. I believe the issue is that the injection token used to retrieve the provider (created here) needs to be the same instance used to create the provider in the client applications. But the injection token isn't exported so clients cant access it. See this "Important Note" on Injection Token docs here I'll try to create and verify a fix locally and if I can I'll raise a PR. Nevermind, someone has beaten me to it #807 |
Beta Was this translation helpful? Give feedback.
-
|
Me too. I didn't have any problems in Angular 19. Also, I don't use standalone components. |
Beta Was this translation helpful? Give feedback.
-
|
ERROR ɵNotFound: NG0201: No provider found for |
Beta Was this translation helpful? Give feedback.
-
|
some one already can use the package? |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
If you update from "@abacritt/angularx-social-login": "^2.4.0" to "@abacritt/angularx-social-login": "^2.5.0", with Angular 20 and the standalone component, you get
No provider found for
InjectionToken SocialAuthServiceConfig. Source: Standalone[_FacebookLoginComponent]. Path: _SocialAuthService -> InjectionToken SocialAuthServiceConfig.I tried with this project
https://github.com/didinj/angular-facebook-login
Beta Was this translation helpful? Give feedback.
All reactions