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
When you are playing music in the web player and start playing music on the desktop player logged into the same account, the service sends this command to tell the web client to pause. I don't think we need to do anything special, seems like it just sends standard track event's when it's unpaused (causing the other client to get the same message themselves) and doesn't refetch the track, however we don't want to throw if it occurs and may want to bubble the event up if api consumers want to use it for some reason.
The text was updated successfully, but these errors were encountered:
When you are playing music in the web player and start playing music on the desktop player logged into the same account, the service sends this command to tell the web client to pause. I don't think we need to do anything special, seems like it just sends standard track event's when it's unpaused (causing the other client to get the same message themselves) and doesn't refetch the track, however we don't want to throw if it occurs and may want to bubble the event up if api consumers want to use it for some reason.
The text was updated successfully, but these errors were encountered: