Angular NG0209 means provider registrations for the same token conflict: the token is configured as both a multi provider and a regular, single-value provider. Check every registration for the token in the relevant injector, then make them consistent with whether the token should resolve to one value or an array of contributions.
What Angular NG0209 means
Angular’s Error Encyclopedia names NG0209 “Invalid multi provider.” Angular’s runtime message for the conflict is “Cannot mix multi providers and regular providers.” In other words, a token is registered using both provider styles in the same relevant injector configuration.
This is different from a missing-provider error: NG0209 concerns incompatible registrations, not the absence of a provider.
How multi providers work
With multi: true, several provider registrations can contribute values to one token. When that token is injected, Angular returns the contributions as an array. The dependency providers guide demonstrates this pattern, and the ConstructorProvider API documents the array result.
Recommended Free Tools
#1 Best Overall
Choose the pattern that matches how the application consumes the token:
- One value: configure the token as a regular provider.
- A collection of contributions: configure each registration for that token as a multi provider.
How to find and fix the conflicting registration
- Read the complete NG0209 error and identify the token it names.
- Search the relevant injector configuration for every registration of that token. Include registrations from imported provider configuration, not just declarations in the file that surfaced the error.
- Decide whether consumers expect a single value or an array of contributions.
- If consumers expect an array, make the contributing registrations consistently use
multi: true. If they expect one value, remove multi-provider configuration for that token and use a regular provider. - Run the application or affected test again and check whether NG0209 is gone. If it remains, look for another registration of the same token in imported configuration or another relevant injector configuration.
The official provider documentation establishes how multi providers contribute values, but it cannot identify which registration causes a particular application’s error. The specific conflict must be found in that application’s provider setup.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Distinguish the error from injection-context problems
NG0209 is specifically the invalid multi-provider diagnostic. Do not treat it as a missing-provider error or a wrong-injection-context error; those describe different dependency-injection problems.
Quick Recap
Rank #3
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
