live state notifications stop when updating to v1.0.0-preview.10 about live-share-sdk

[ryanbliss]

I think I might know what the issue here. Are you calling liveState.set(undefined), and is that when the listener isn't being called? Or have you tried setting it to other values, such as a string or object?

Knowing what values are being passed in as your initial state and set param would be super helpful, thanks!!

[mscherotter]

I am not calling liveState.set(undefined) . I always call liveState set with a JSON object.

[mscherotter]

Do all members need to call livestate.initialize()? What state parameters should I specify if I don't want visitors to update the live state?

[mscherotter]

I was just able to fix it by calling initialize() for the visitors as well as the host, even though I don't want to set the state for the visitors.

[ryanbliss]

Hey Michael, the initial state on .initialize() is not broadcasted out and will not trigger a changed event. It is just the default state, which you could make undefined in the initializerc and when the presenter connects you can then call .set("whatever") on their client. Even if someone joins late, the initial state will not override what was there beforehand.

It's just a default value, since many use cases you don't want to have to have state start as undefined (eg countState.initialize(0)). The default state will be at that initial state until the remote state starts coming in, which will always override that default value.

[ryanbliss]

And yes, for all of our DDS's, all users need to call .initialize(), since that is what starts listening for socket events.