unpublish call on host causes to fire user-left event in remote audience about agorawebsdk-ng HOT 5 CLOSED

Thanks for your feedback.

The user-left event was fired because we need to use this event to trigger the Agora Native SDK's decoder releasing. I think this is a bad design because this workaround will affect the customer's application logic.

We are planning to solve it in v0.2.0, just like #8 , we will redesign the unpublish mechanism in v0.2.0.

from agorawebsdk-ng.

Thanks for the reply. Do you have any hints or suggestions on how applications can distinguish unpublishing and channel leaving at this point?

Related SO question -
https://stackoverflow.com/questions/62027242/the-user-left-event-is-fired-when-unpublish-method-is-called

from agorawebsdk-ng.

There are two differences between unpublishing and leaving channel:

• user-left event's reason param. If the remote peer is unpublished, reason will be "BecomeAudience"
• if this user-left event is caused by the remote peer unpublishing, you will receive user-joined about 10s after receiving user-left

So if you receive a user-left with "BecomeAudience" and receive user-joined in 10s, it is unpublishing, otherwise, it is channel leaving.

from agorawebsdk-ng.

This definitely can address the application logic issues until the SDK v2 is brought out.

In fact, BecomeAudience is enough for the application to change its state correctly and the subsequent user-joined is the lifesaver it can use.

Great patch!

from agorawebsdk-ng.

This issue has been fixed in v4.0.0( release note)

from agorawebsdk-ng.