Feature Request - localParticipant.unpublishTrack(track) promise

[jpodwys]

Today, localParticipant.publishTrack(track) returns a promise while localParticipant.unpublishTrack(track) does not. Being unable to await a promise results in bug reports like #1227. I also wonder if this is why issues like #656 and #1007 were created.

This is especially problematic when a consumer's application uses the same custom track name such as "camera" or "screen" for both the just-unpublished and newly-published tracks because Twilio throws an error when a single participant publishes two tracks using the same name.

Twilio-Video users can work around this issue in a number of ways including

1. Append random characters to the end of hard-coded track names then manage those extra characters as you see fit
2. Catch publishTrack errors, check if they're due to a duplicate track issue, wait for an arbitrary delay, then attempt to publish again

It would be great if Twilio instead provided some means of knowing when a track is fully unpublished.

To avoid breaking changes, perhaps a new unpublishTrackAsync method could be introduced.

Thank you!

[luisrivas]

Hi @jpodwys

Thank you for reporting this issue and for taking the time to explain it so clearly. We will evaluate the best approach to fix this.