Skip to content
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

NullInjectorError: No provider for Firestore2! #55309

Closed
CrissCriss-01 opened this issue Apr 12, 2024 · 2 comments
Closed

NullInjectorError: No provider for Firestore2! #55309

CrissCriss-01 opened this issue Apr 12, 2024 · 2 comments

Comments

@CrissCriss-01
Copy link

Describe the problem that you experienced

I created a new Angular 17 project from scratch. Then integrated Firebase just to see if it is working -> it works!
Then I added all my files and components, all are standalone: true
When running ng serve from vs code, now I get this error:

R3InjectorError(Standalone[_AppComponent])[Firestore2 -> Firestore2 -> Firestore2]:
NullInjectorError: No provider for Firestore2!

Attached my app.component.ts file

appComponent

Enter the URL of the topic with the problem

No response

Describe what you were looking for in the documentation

No response

Describe the actions that led you to experience the problem

No response

Describe what you want to experience that would fix the problem

No response

Add a screenshot if that helps illustrate the problem

No response

If this problem caused an exception or error, please paste it here

No response

If the problem is browser-specific, please specify the device, OS, browser, and version

No response

Provide any additional information here in as much as detail as you can

No response

@JeanMeche
Copy link
Member

Hello, we reviewed this issue and determined that it doesn't fall into the bug report or feature request category. This issue tracker is not suitable for support requests, please repost your issue on StackOverflow using tag angular.

If you are wondering why we don't resolve support issues via the issue tracker, please check out this explanation.

@JeanMeche JeanMeche closed this as not planned Won't fix, can't repro, duplicate, stale Apr 12, 2024
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators May 13, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants