Thanks for your response. I agree that it appears that zoomOSC is getting stuck but I am certain an error should be returned. I execute all the commands to the SDK in a syncronus block, and ensure that a small delay is applied (as discussed in the other post),
My log (from our app) is showing the below, I have commented for reference:
Info: received message /zoom/users/username/addSpot “1” “2” “3”. //request to add those three users to spotlight
Info: Spot-lit User. //first user commadn executed, Success must have been returned otherwise we would log an errror
Info: Spot-lit User //second user commadn executed, Success must have been returned otherwise we would log an errror
Info: Spot-lit User //third user commadn executed, Success must have been returned otherwise we would log an errror
Info: got spotlight change for user 16778240 to 1 //and then finally we get the notification that the first spotlight change has occurred. The SDK doesn’t even attempt the other two.
So the command is returning success even when it does nothing - which is obviously not correct.
It’s a really tricky one for us to fix without adding in some very clunky extra code for this specific edge case.
It’s worth noting that adding users to the Pin works as expected, with failure responses until the pin command is successful.