disposable-callback-not-disposed.md

DisposableCallback was not disposed

Components that descend from FluxorComponent or FluxorLayout automatically subscribe to the StateChanged event on every IState<TState> and IStateSelection<TState, TValue> property in the component automatically. When the component is disposed, this subscription is removed, to avoid memory leaks.

If ever you see an error message like the following

DisposableCallback with Id "(Some text here)" was not disposed.

it is most likely because of one of the following reasons:

Not calling base.Dispose

Problem: You have overridden Dispose(bool disposed) on FluxorComponent or FluxorLayout and not called base.Dispose(disposed).

Fix: If you override a method, make sure you call the base method.

protected override void Dispose(bool disposed)
{
  base.Dispose(disposed);
  // etc
}

Not calling base.BeginMiddlewareChange

Problem: In more advanced scenarios, you have called IStore.BeginInternalMiddlewareChange without disposing the result.

Fix: If you execute a method that returns an IDisposable, make sure you dispose it. Note that the following example is for advanced use cases only (middleware).

using (Store.BeginMiddlewareChange())
{
  //etc
}

Not calling Dispose on IActionSubscriber.GetActionUnsubscriberAsIDisposable

Problem: You have called IActionSubscriber.GetActionUnsubscriberAsIDisposable() and not called Dispose() on the result.

Fix: You must call Dispose

Mismatch Between Async/Sync Initialization methods

If you use OnInitializedAsync you should call base.OnInitializedAsync() and not the base.OnInitialized().