IonToggle and IonRadioGroup are now giving RuntimeError: NG01203: No value accessor for form control name: <controlname> for reactive forms

peterjc · August 19, 2025, 11:16am

I have quite a large form, which includes the above elements. No, after going to standalone, those controls only give me the No value accessor error.

All other controls work fine, including IonTextArea, and these use to work. The control is there, and has the correct value (true)

It has the correct name, but valueAccessor is null

I created a new Ionic app with a form and the above elements worked fine.

My question is how can I possibly diagnose why I have this problem in my application. I can see the control should have this (source below), so I am stumped as to why it is null for me, and how can I find out why. I can’t provide a simple example, as it works in a new simple example, but not in my project I have been converting to standalone.

And why just these to control, and not all the others?

Anyone have any suggestions on how to diagnose?

Thanks in advance

github.com/ionic-team/ionic-framework

packages/angular/standalone/src/directives/toggle.ts

1899b49d2

import {
  ChangeDetectionStrategy,
  ChangeDetectorRef,
  Component,
  ElementRef,
  EventEmitter,
  HostListener,
  Injector,
  NgZone,
  forwardRef,
} from '@angular/core';
import { NG_VALUE_ACCESSOR } from '@angular/forms';
import { ValueAccessor, setIonicClasses } from '@ionic/angular/common';
import type { ToggleChangeEventDetail, Components } from '@ionic/core/components';
import { defineCustomElement } from '@ionic/core/components/ion-toggle.js';

import { ProxyCmp, proxyOutputs } from './angular-component-lib/utils';

const TOGGLE_INPUTS = [
  'checked',

This file has been truncated. show original

peterjc · August 20, 2025, 12:22am

Ah, my problem was I had not imported these 2 components…

Strange, normally the IDE show s red error if I have missed any,

Anyway, now they are imported, and makes sure they are from standalone, it all works

Topic		Replies	Views
Error when using [(ngModel)]: No value accessor for '' ionic-v3	6	5422	August 22, 2016
Karma + Ionic 4 - No value accessor for form control with name Ionic Framework	3	13230	January 8, 2020
No value accessor for 'username' ionic-v3	3	2424	July 9, 2016
After Upgrading beta 11 : No value accessor for 'email' error ionic-v3	2	1189	August 12, 2016
No value accessor for '' ionic-v3	0	397	August 8, 2016

IonToggle and IonRadioGroup are now giving RuntimeError: NG01203: No value accessor for form control name: <controlname> for reactive forms

Related topics