Change detection non working for side-effects triggered by onFileDrop when destroying component

[ellesse]

ngx-file-drop: 11.0.2

Used in conjunction with @ngrx/store, @ngrx/effects and @ngrx/entity (10.1.2).

Description of the issue:

• The onFileDrop emitted event triggers an action that in its turn starts a side effect to upload the content of the file
• while the content is uploaded, the ngx-file-drop component is removed from the parent view (the component itself being wrapped inside an *ngIf directive whose clause becomes false).
• After the content upload operation is successfully completed, the store is correctly updated and the observables bound to store features emit the new values as expected. Despite this, change detection in the parent component is not working anymore, with async pipes not returning the new emitted values, unless the user performs some action (e.g. button click) that triggers a new state change.
• if the file is uploaded by using the native file input, the issue does not occur and the view is updated correctly.
• The issue also does not occur if the ngx-file-drop is just hidden with display:none and not removed during the content upload operation.

[jcarlin]

Yep, I can confirm, we are experiencing the same thing here.