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
Actions from actionQueue are sometimes dispatched multiple times
Expected Behavior
What do you expect should be happening?
Every action from actionQueue should be dispatched only once
How to reproduce
When "@@network-connectivity/CONNECTION_CHANGE" action queue to be flushed is created. If action inside that queue dispatches "@@network-connectivity/CHANGE_QUEUE_SEMAPHORE", payload "GREEN"( as the readME recommends if you want to wait an action to complete before the next action). Due to the action being intercepted by the library a secondary queue will be created and those both are ran simultaneously. Nothing is done to check if certain action is already removed from the actual state or queue is already being flushed. This causes X amount of actions to be dispatched multiple times depending on the queue size.
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
queueReleaseThrottle was 2000, looks like using default 50 is solve problem, but there is still principal problem with waiting this throttle time in middleware.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Closing this issue after a prolonged period of inactivity. If this is still present in the latest release, please feel free to create a new issue with up-to-date information.
Current Behavior
Actions from actionQueue are sometimes dispatched multiple times
Expected Behavior
Every action from actionQueue should be dispatched only once
How to reproduce
When "@@network-connectivity/CONNECTION_CHANGE" action queue to be flushed is created. If action inside that queue dispatches "@@network-connectivity/CHANGE_QUEUE_SEMAPHORE", payload "GREEN"( as the readME recommends if you want to wait an action to complete before the next action). Due to the action being intercepted by the library a secondary queue will be created and those both are ran simultaneously. Nothing is done to check if certain action is already removed from the actual state or queue is already being flushed. This causes X amount of actions to be dispatched multiple times depending on the queue size.
The text was updated successfully, but these errors were encountered: