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
Encountering a NullInjectorError: No provider for _RadioControlRegistry! error when using @defer block #54117
Comments
The `RadioControlRegistry` was only provided in a module, providedIn: 'root' fixes that issue. Fixes angular#54117
Hi, thanks for taking the time for providing a reproduction. I believe I have found the root cause and provided a fix in #54130 |
The `RadioControlRegistry` was only provided in a module, providedIn: 'root' fixes that issue. Fixes angular#54117
The `RadioControlRegistry` was only provided in a module, providedIn: 'root' fixes that issue. Fixes angular#54117 Co-authored-by: sr5434 <s98775763@gmail.com>
The `RadioControlRegistry` was only provided in a module, providedIn: 'root' fixes that issue. Fixes angular#54117 Co-authored-by: sr5434 <s98775763@gmail.com>
The `RadioControlRegistry` was only provided in a module, providedIn: 'root' fixes that issue. Fixes angular#54117 Co-authored-by: sr5434 <118690585+sr5434@users.noreply.github.com>
The root cause of this issue is #52876, so we'll close this as effectively a duplicate. |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Which @angular/* package(s) are the source of the bug?
core
Is this a regression?
Yes
Description
Encountering a NullInjectorError: No provider for _RadioControlRegistry! error when using an input type="radio" element within a component that is defer loaded using the @ defer block in Angular. This issue seems to prevent radio button functionality within defer-loaded components
Please provide a link to a minimal reproduction of the bug
https://stackblitz.com/~/github.com/surajchopra1234/demo
Please provide the exception or error you saw
Please provide the environment you discovered this bug in (run
ng version
)Anything else?
No response
The text was updated successfully, but these errors were encountered: