ExpressionChangedAfterItHasBeenCheckedError

[tatsujb]

this lib is lifting the typical Angualr 5+ error of state change after check :

error message :

Error: ExpressionChangedAfterItHasBeenCheckedError: Expression has changed after it was checked. Previous value: 'ngForOf: undefined'. Current value: 'ngForOf: leftTop,leftCenter,leftBottom,rightTop,rightCenter,rightBottom,centerTop,centerCenter,centerBottom'.
    at viewDebugError (core.js:7393)
    at expressionChangedAfterItHasBeenCheckedError (core.js:7381)
    at checkBindingNoChanges (core.js:7483)
    at checkNoChangesNodeInline (core.js:10344)
    at checkNoChangesNode (core.js:10333)
    at debugCheckNoChangesNode (core.js:10936)
    at debugCheckDirectivesFn (core.js:10864)
    at Object.eval [as updateDirectives] (SnotifyComponent.html:formatted:1)
    at Object.debugUpdateDirectives [as updateDirectives] (core.js:10853)
    at checkNoChangesView (core.js:10232)

pointing to this :

<div class="snotify-backdrop" *ngIf="backdrop >= 0" [style.opacity]="backdrop"></div>
<div *ngFor="let position of notifications | keys" class="snotify snotify-{{position}}">
    <!-- FAULTY --><ng-snotify-toast *ngFor="let notification of notifications[position] | slice:blockSize_a:blockSize_b" [toast]="notification" (stateChanged)="stateChanged($event)"></ng-snotify-toast>
</div>

this need to be fixed to meet angular's specs.

[Nexeuz]

Same problem

[siddhsuk]

Same Issue...! When this can be fixed?

[abdullaunais]

I have the same error, but everything works as expected. (Angular 6)

[tatsujb]

same : https://github.com/artemsky/ng-snotify/issues/51 guys I think we're better off moving to another lib @artemsky has'nt responded in nearly a year.

[AndyOR-Apis]

Same error in Angular 7. Notifications still work as expected but this error is the only one being thrown in the entire application and means it can't be put through to production (Zero error policy).

Shame to see such a good library die out after all the work that must have gone into it's development.

[CristianFlaviu]

same problem,I am using Angular 11