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
I think I found a bug, but before I dig deeper I want to make sure I'm not overlooking something obvious or if this may be even expected behaviour.
Given the following code I would expect that disposing the signal, an interrupted event would be fired:
This works as long as we are not creating a strong reference to the observer like observerStrongRef does.
If we keep a strong reference to observer, signalProducerLifetimeEnded is fulfilled but signalInterrupted is not.
After removing observerStrongRef, signalInterrupted will fulfill and the test passes.
Is this a bug?
I'm using ReactiveSwift 6.6.0
Thanks
David
The text was updated successfully, but these errors were encountered:
Okay I think I got it now.
Without a strong reference to the observer, the observer is deinitialised almost immediately which will fire an interrupted event.
Disposing a signal will not fire an interrupted event.
I thought that disposing a signal will also fire an interrupted event.
Hey,
I think I found a bug, but before I dig deeper I want to make sure I'm not overlooking something obvious or if this may be even expected behaviour.
Given the following code I would expect that disposing the signal, an interrupted event would be fired:
This works as long as we are not creating a strong reference to the observer like
observerStrongRef
does.If we keep a strong reference to
observer
,signalProducerLifetimeEnded
is fulfilled butsignalInterrupted
is not.After removing
observerStrongRef
,signalInterrupted
will fulfill and the test passes.Is this a bug?
I'm using ReactiveSwift
6.6.0
Thanks
David
The text was updated successfully, but these errors were encountered: