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
This is expected behavior. These multiple executions are due to the client reconnecting (this is due to an idle connection). So it resyncs and gets the data back. If the connection is not idle, i.e if there are messages in transit then this won't happen. You can confirm by logging the didConnect callbacks. Also the way to work around it is to do the following:
The callbacks of downlinks opened using the swim client are being executed multiple times.
Tested with a map downlink with
didUpdate
callback and a value downlink with adidSet
callback.The text was updated successfully, but these errors were encountered: