94

I know there are a lot of same questions already posted in stack-overflow and tried different solutions to avoid the run-time error but None of them are working for me.

Error

Component and Html Code

export class TestComponent implements OnInit, AfterContentChecked {
    @Input() DataContext: any;
    @Input() Position: any;
    sampleViewModel: ISampleViewModel = { DataContext: : null, Position: null };
    constructor(private validationService: IValidationService, private modalService: NgbModal, private cdRef: ChangeDetectorRef) {
    }

    ngOnInit() {

    }
    ngAfterContentChecked() {

            debugger;
            this.sampleViewModel.DataContext = this.DataContext;
            this.sampleViewModel.Position = this.Position;

    }


<div class="container-fluid sample-wrapper text-center" [ngClass]="sampleViewModel.DataContext?.Style?.CustomCssClass +' samplewidget-'+ sampleViewModel.Position?.Columns + 'x' + sampleViewModel.Position?.Rows">
     //some other html here
</div>

Please Note : This Component is loaded dynamically using DynamicComponentLoader

After My trouble shooting I have identified couple of issues

First of all this child component is loaded dynamically by using DynamicComponentResolver and passing the input values like below

 ngAfterViewInit() {
    this.renderWidgetInsideWidgetContainer();

  }


  renderWidgetInsideWidgetContainer() {
    let component = this.storeFactory.getWidgetComponent(this.dataSource.ComponentName);
    let componentFactory = this._componentFactoryResolver.resolveComponentFactory(component);
    let viewContainerRef = this.widgetHost.viewContainerRef;
    viewContainerRef.clear();
    let componentRef = viewContainerRef.createComponent(componentFactory);
    debugger;
    (<IDataBind>componentRef.instance).WidgetDataContext = this.dataSource.DataContext;
    (<IDataBind>componentRef.instance).WidgetPosition = this.dataSource.Position;

  }

Even If I changed my child component html like below I am getting this same error.Just add a angular ngclass attribute

<div class="container-fluid ds-iconwidget-wrapper text-center" [ngClass]="Sample">

</div>

My databinding and everything are working fine.Do I need to do anything on parent component? I already tried all the lifecyle events in child component

Shahid
  • 460
  • 1
  • 7
  • 21
Code-EZ
  • 6,514
  • 11
  • 44
  • 72

11 Answers11

120

you have to tell angular that you updated the content after ngAfterContentChecked you can import ChangeDetectorRef from @angular/core and call detectChanges

import {ChangeDetectorRef } from '@angular/core';

constructor( private cdref: ChangeDetectorRef ) {}


ngAfterContentChecked() {

this.sampleViewModel.DataContext = this.DataContext;
this.sampleViewModel.Position = this.Position;
this.cdref.detectChanges();

 }
candidJ
  • 3,972
  • 1
  • 20
  • 28
Richie Fredicson
  • 1,742
  • 2
  • 12
  • 16
61

The ngAfterContentChecked lifecycle hook is triggered when bindings updates for the child components/directives have been already been finished. But you're updating the property that is used as a binding input for the ngClass directive. That is the problem. When Angular runs validation stage it detects that there's a pending update to the properties and throws the error.

To understand the error better, read these two articles:

Think about why you need to change the property in the ngAfterViewInit lifecycle hook. Any other lifecycle that is triggered before ngAfterViewInit/Checked will work, for example ngOnInit or ngDoCheck or ngAfterContentChecked.

So to fix it move renderWidgetInsideWidgetContainer to the ngOnInit() lifecycle hook.

Max Koretskyi
  • 85,840
  • 48
  • 270
  • 414
  • why are you updating the property in the `ngAfterViewInit/Checked`? – Max Koretskyi Aug 02 '17 at 18:09
  • Actully it's not updating I am setting my input data to a viewmodel and finally all the properties are binded through this model like wrapper class. When I directly bind the @Input datacontext I am getting this same error. is there is no workaround to get rid of this error through any of the life cycle events.Let me try ngAfterViewInit/Checked mentioned in your answer – Code-EZ Aug 02 '17 at 18:13
  • 3
    try `ngOnInit` or `ngDoCheck` or `ngAfterContentChecked.` If it's still not working, create a plunker – Max Koretskyi Aug 02 '17 at 18:16
  • hmm..It's weird for me , as per my understanding it's pretty straight forward scenario. I am suspecting it's because of dynamic Component loader. Let me try to create a plunker. – Code-EZ Aug 02 '17 at 18:28
  • I have tried all the life cycle events but unfortunately i couldn't fix the issue. but my question is updated by adding more points after my trouble shooting. hope this will helps you to get some idea. – Code-EZ Aug 02 '17 at 19:22
  • i need a plunker – Max Koretskyi Aug 02 '17 at 20:01
  • @Code-EZ Why is this chosen as the selected answer if you didn't get it to work? Or did you eventually get it to work? – rooby Jan 16 '19 at 08:14
  • @rooby, maybe because I explained the cause of the error and the exact solutions heavily depend on the application design – Max Koretskyi Feb 01 '19 at 17:52
  • @rooby after moved to ngOnInit() ,it's worked. You can see my comments with Maxim. – Code-EZ Feb 20 '19 at 05:04
  • 1
    For me work in ngOnInit only after i used a reference variable instead of a directory, like explaned here https://stackoverflow.com/questions/48330760/cannot-read-property-viewcontainerref-of-undefined – dgraf Jul 31 '20 at 16:07
12
 ngAfterViewInit() {
   setTimeout(() => {
     this.renderWidgetInsideWidgetContainer();
   }, 0);
  }

That is a good solution to resolve this problem.

Jviaches
  • 838
  • 3
  • 14
  • 29
  • 1
    None of the other solutions worked for my specific esoteric case so after a couple of hours I gave up and had to resort to this and it worked. – svarog Feb 25 '21 at 16:08
  • I didn't understand how but it worked for me too. – Fatih Ersoy Apr 15 '21 at 08:45
  • 2
    @FatihErsoy you can think of setTimeout() as putting something at the end of the overall JS event queue. So in this case, even with a Timeout of "0," it puts the code to run at the end of the events to run which means the code in Timeout will likely run after the Angular render code which is further ahead in the queue. Ultimately, setTimeout() feels like a hack solution, but when the Angular lifecycles aren't behaving as you expect and you're desperate to get it working then it's a tool you can resort to using. – Jeff Gilliland Apr 30 '21 at 09:17
  • I had this issue while loading a dialog component, with a list of checkboxes. By wrapping my code into the `setTimeout()` function, the dialog display is delayed long enough to get rid of that error. – AllJs May 20 '21 at 02:53
11

If you are using <ng-content> with *ngIf you are bound to fall into this loop.

Only way out I found was to change *ngIf to display:none functionality

bresleveloper
  • 5,430
  • 3
  • 31
  • 45
6

I was having trouble with .

ERROR: ExpressionChangedAfterItHasBeenCheckedError: Expression has changed after it was checked. Previous value for 'mat-checkbox-checked': 'true'. Current value: 'false'.

The Problem here is that the updated value is not detected until the next change Detection Cycle runs.

The easiest solution is to add a Change Detection Strategy. Add these lines to your code:

import { ChangeDetectionStrategy } from "@angular/core";  // import

@Component({
  changeDetection: ChangeDetectionStrategy.OnPush,
  selector: "abc",
  templateUrl: "./abc.html",
  styleUrls: ["./abc.css"],
})
4

Two Solutions:

  1. Make Sure if you have some binding variables then move that code to settimeout( { }, 0);
  2. Move your related code to ngAfterViewInit method
Chetan Laddha
  • 847
  • 7
  • 19
  • It depends as it moves your code to the event queue and it will get executed when the current execution finishes. JavaScript is a single-threaded scripting language, so it can execute one piece of code at a time (due to its single-threaded nature) each of these blocks of code is “blocking” the progress of other asynchronous events. The settimeout code will be executed only when your current code finishes your execution. – Chetan Laddha May 22 '19 at 06:54
4

*NgIf can create problem here , so either use display none css or easier way is to Use [hidden]="!condition"

Pragati Dugar
  • 165
  • 1
  • 7
3
setTimeout(() => { // your code here }, 0);

I wrapped my code in setTimeout and it worked

Andris
  • 2,251
  • 19
  • 23
2

I had the same issue trying to do something the same as you and I fixed it with something similar to Richie Fredicson's answer.

When you run createComponent() it is created with undefined input variables. Then after that when you assign data to those input variables it changes things and causes that error in your child template (in my case it was because I was using the input in an ngIf, which changed once I assigned the input data).

The only way I could find to avoid it in this specific case is to force change detection after you assign the data, however I didn't do it in ngAfterContentChecked().

Your example code is a bit hard to follow but if my solution works for you it would be something like this (in the parent component):

export class ParentComponent implements AfterViewInit {
  // I'm assuming you have a WidgetDirective.
  @ViewChild(WidgetDirective) widgetHost: WidgetDirective;

  constructor(
    private componentFactoryResolver: ComponentFactoryResolver,
    private changeDetector: ChangeDetectorRef
  ) {}

  ngAfterViewInit() {
    renderWidgetInsideWidgetContainer();
  }

  renderWidgetInsideWidgetContainer() {
    let component = this.storeFactory.getWidgetComponent(this.dataSource.ComponentName);
    let componentFactory = this.componentFactoryResolver.resolveComponentFactory(component);
    let viewContainerRef = this.widgetHost.viewContainerRef;
    viewContainerRef.clear();
    let componentRef = viewContainerRef.createComponent(componentFactory);
    debugger;
    // This <IDataBind> type you are using here needs to be changed to be the component
    // type you used for the call to resolveComponentFactory() above (if it isn't already).
    // It tells it that this component instance if of that type and then it knows
    // that WidgetDataContext and WidgetPosition are @Inputs for it.
    (<IDataBind>componentRef.instance).WidgetDataContext = this.dataSource.DataContext;
    (<IDataBind>componentRef.instance).WidgetPosition = this.dataSource.Position;
    this.changeDetector.detectChanges();
  }
}

Mine is almost the same as that except I'm using @ViewChildren instead of @ViewChild as I have multiple host elements.

rooby
  • 362
  • 7
  • 19
1

This code solved my Problem.

import {ChangeDetectorRef } from '@angular/core';

constructor( private cdref: ChangeDetectorRef ) {}

ngAfterContentChecked() {
  this.cdref.detectChanges();
}
-2

Try this, to call your code in ngOnInit()

someMethod() // emitted method call from output
{
    // Your code 
}

ngOnInit(){
  someMethod(); // call here your error will be gone
}
SURENDRANATH S
  • 1,207
  • 12
  • 22