Skip to content

track id uuid postfix prevents association in amazon-chime-sdk-js #647

@ian-luca

Description

@ian-luca

YOU MUST read first!

Please use Community Forum for general technical discussions and questions.

  • I have used Google with the error message or bug in association with the library and Cordova words to make sure the issue I'm reporting is only related to iOSRTC.
  • I have provided steps to reproduce (e.g. using sample app code https://github.com/cordova-rtc/cordova-plugin-iosrtc-sample or updated extra/renderer-and-libwebrtc-tests.js file).
  • I have provided versions of third party library name, ios, Xcode and plugin version and adapter.js version if used.

Note: If the checkboxes above are not checked (which you do after the issue is posted), the issue will be closed, removing this checkbox will result in automatic closed issue.

Versions affected

  • Cordova version: 10.0.0
  • Cordova iOS version: 6.2.0
  • Plugin version: 6.0.18
  • iOS version: 14.4
  • Xcode version: 12.4 (12D4e)
  • WebRTC-adapter version: -
  • WebRTC Framework version: amazon-chime-sdk-js 2.4.0

Description

When using cordova-plugin-iosrtc with amazon-chime-sdk-js the iOS user cannot see other meeting participants. It seems that in the plugin track ids are appended by uuids which makes it impossible for the chime sdk to associate the there called subscription acknowledgement tracks with the actual tracks. (maybe related to #432?)

Steps to reproduce

In short: join a meeting with other participants

When joining a chime meeting, chime subscribes to other users tracks (https://github.com/aws/amazon-chime-sdk-js/blob/a8a5413688e04e57266fc9c4da709b6a89bb7a35/src/task/SubscribeAndReceiveSubscribeAckTask.ts#L92) where tracks are referenced as track_video or track_video_13 for example. At this point in https://github.com/aws/amazon-chime-sdk-js/blob/a8a5413688e04e57266fc9c4da709b6a89bb7a35/src/videostreamindex/DefaultVideoStreamIndex.ts#L85 they are associated with the meeting attendee. So far so good.
But at the "received track event" track ids are postfixed with a uuid and can therefore not be associated with an attendee or a stream.

Expected results

track ids should not be postfixed with a uuid. Or atleast there should be an option to configure it in some way to work with multiple sdks/libs.

Actual results

track ids cannot be associated to what the lib originally intended.

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions