You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If an message gets queued in the the angular ErrorHandler.handleError(error: any) method,
the notification will not get rendered until some other page change.
Workaround:
To display the message instantly a force change detection can be triggered with (<any>this.notifierContainer).changeDetector.detectChanges();
I stumbled upon the same issue and found a fix on the Angular2-Toaster project page.
They describe that you should run the call within an ngZone.run(...) block.
If an message gets queued in the the angular ErrorHandler.handleError(error: any) method,
the notification will not get rendered until some other page change.
Workaround:
To display the message instantly a force change detection can be triggered with
(<any>this.notifierContainer).changeDetector.detectChanges();
The text was updated successfully, but these errors were encountered: