aws / amazon-chime-sdk-js Goto Github PK

What are you trying to do?

I would like to Add the javascript to my app dynamically instead of through npm so as to reduce my app's footprint. I'm looking for a link similar to this: https://sdk.amazonaws.com/js/aws-sdk-2.648.0.min.js

How can the documentation be improved to help your use case?

Provide a link for downloading the sdk minified js directly

What documentation have you looked at so far?

all of it

https://github.com/aws/amazon-chime-sdk-js/blob/master/src/audiovideocontroller/DefaultAudioVideoController.ts#L333

This should return Left instead:

https://github.com/aws/amazon-chime-sdk-js/blob/master/src/meetingsession/MeetingSessionStatusCode.ts#L13

Important: Please attach INFO-level logs with timestamps to the report from before the session started up until the point at which the unexpected behavior occured. For multi-participant calls, attach a log file for each participant if possible.
screenshare-toggeled-bug.log

Meeting and attendee IDs:
List the meeting and attendee IDs that the attached logs apply to.
MeetingId: ab05ded2-b910-4a8d-8404-2fac42330a99
AttendeeId: e19373bd-8d97-46c4-9204-40a46ae55bfe
Timeline
Outline the main actions the user performed and when:

• 2019-11-26T19:28:23.437Z DefaultScreenShareFacadeStop
• 2019-11-26T19:28:23.541Z received StreamEnd
• 2019-11-26T19:28:23.543Z DefaultScreenViewingDeltaRenderer: Closing

Describe the bug
Describe the bug and the timestamp at which it happened relative to the timestamp in the log file.

As seen above, DefaultScreenViewingDeltaRenderer is closed when screenshare stops. This closes screen viewing.

Screenshots
If applicable, add screenshots to help explain the problem.

Platform

• OS: Mojave 10.14.6
• Browser: Chrome
• Browser Version: 78.0.3904.108
• Amazon Chime SDK GitHub Commit: fbabb46

Important: Please attach INFO-level logs with timestamps to the report from before the session started up until the point at which the unexpected behavior occurred. For multi-participant calls, attach a log file for each participant if possible.

Describe the bug

A realtime error was encountered due to the active speaker detector throwing an error. This occurred for all participants and caused their meeting sessions to tear down.

Log: realtime-error.log

INFO-level logs:
DeviceChangeObserverNotCalledBug.log

The above logs show an absence of logs for listAudioInputDevices which should have been called when I plugged in my headset.

Meeting and attendee IDs:
"MeetingId": "6171c575-8311-4cdf-a8dc-079b6cc250c1"
"AttendeeId": "7f46ac0f-8d7a-4894-9844-ba9b9fe79246"

Timeline
Outline the main actions the user performed and when:

• 2019-12-10T01:22:39.575Z Plugged in headset (Followed by absence of listAudioInputDevices logs)

Describe the bug
The device change observer is not being called when device Id is the same.

Platform

• OS: MacOS Mojave 10.14.6
• Browser: Chrome
• Browser Version: 78.0.3904.108
• Amazon Chime SDK GitHub Commit: 7390b86

From #198

Describe the bug
This seems to be caused by Firefox's limitation for getUserMedia API, for example, on my MacOS, getUserMedia request can only return a video of resolution 1280x720 or 640x480 on Firefox.

What resolution do you choose for the video preview ?

Screenshots
If applicable, add screenshots to help explain the problem.

Platform

• OS:
• Browser:
• Browser Version:
• Amazon Chime SDK GitHub Commit:

Describe the bug
Some tests use DOM mock behavior that create timeouts. These timeouts sometimes expire after the test finishes and can lead to unpredictable tests since the DOMMock may cleanup before then.

The first thing to do would be to fix existing failures when running npm run test:slow.

We may want to strictly sequence changes to the global DOM object so that it is not possible for tests to step on each other as easily.

Platform

• OS:
• Browser:
• Browser Version:
• Amazon Chime SDK GitHub Commit:

Important: Please attach INFO-level logs with timestamps to the report from before the session started up until the point at which the unexpected behavior occured. For multi-participant calls, attach a log file for each participant if possible.

Meeting and attendee IDs:
List the meeting and attendee IDs that the attached logs apply to.
Conference id : cd9c6f8a-d1d2-4832-8cc6-24cb4ab948ae

Timeline
Outline the main actions the user performed and when:

• Join a meeting in safari
• Join the same meeting in another tab or on a different instance of safari on same machine.
• Both the participants will appear on the roster of second tab.
• After few seconds the first participant will drop from the meeting

Describe the bug
Describe the bug and the timestamp at which it happened relative to the timestamp in the log file.
[Warning] 2020-01-10T03:09:36.800Z [WARN] SDK - reconnection recommended due to: no packets received: true, missed pongs: false, bad audio delay: false

Screenshots
If applicable, add screenshots to help explain the problem.

Platform

• OS: MAX
• Browser: Safari
• Browser Version: 13.0.4
• Amazon Chime SDK GitHub Commit: 976132711fa5d55783fb1d9f29a7e5240e1dc9ce
  safari_bu_logs_latest.log

Hi,

I don't know if this is the right place to ask this question. But, I would like to know how we can integrate services like AWS Transcribe, Rekogntion with chime sdk. Specifically, I'd like to know how to send the audio/video to these services to get responses. Any pointers would be very much appreciated.

Thanks

What are you trying to do?

Currently the minimal demo application is incomplete so its not clear what the purpose is. Perhaps we can use it to demonstrate as a simple Vanilla JS demo app. This would require to be clear.

How can the documentation be improved to help your use case?

The existing documentation doesn't make the intention of this demo clear.

What documentation have you looked at so far?

README.md, Amazon Chime SDK Developer Guide, etc.

Hi,

I am integrating chime SDK in a Laravel project. Is there any demo available in javascript version instead of typescript(https://github.com/aws/amazon-chime-sdk-js/tree/master/demos/browser)?

Thanks

What are you trying to do?

When multiple monitors are plugged in - sometimes screen sharing doesnt begin unless the presenter actively interacts with the screen.

Platform

OS: win10
Browser: chrome
Browser Version: 79
Amazon Chime SDK GitHub Commit: 6afdca0

This is not specific to Chime SDK and could be reproed with an independent WebRtc app. https://janus.conf.meetecho.com/screensharingtest.html

How can the documentation be improved to help your use case?

Call out in the API or so that this is a limitation of the browser and not a chime SDK bug

What documentation have you looked at so far?

README.md, Amazon Chime SDK Developer Guide, etc.

Using the latest Chrome browser, running demo meetingV2, and clicking the "Share" button, I do get a popup where I can select e.g. the entire screen to share, however, after clicking the "Share" button of the popup, nothing appears to be shared.

The javascript console shows the following error:

systemDefaultContentShareController.js:24 Uncaught (in promise) DOMException: Permission denied by system

Is there a way to test whether the user can share content to begin with, before showing the popup? Or, could a callback be added (perhaps in the ContentShareObserver) that is called whenever it turns out sharing is not permitted by the system?

Sometimes on Chrome and Chromium there is no attendee presence event generated when joining without an audio device.

Need to add media recording feature in demos/browser/meeting

For example: User wants to start pause and end media recording.

How can the documentation be improved to help your use case?

For example: Include a section where example of Media recording is already explained how to use.

DefaultVideoStreamIndex "lazily" computes media stream mappings. It is also responsible for computing the streams that client wants to subscribe.

It's better that the subscription calculation algorithm is componentized to allow dynamic configuration of subscription algorithm.

VideoStreamIndex should also keep stream allocation information for consistency with server.

Important: Please attach INFO-level logs with timestamps to the report from before the session started up until the point at which the unexpected behavior occurred. For multi-participant calls, attach a log file for each participant if possible.

Logs: reconnect-loop.txt

Describe the bug
Unplugging explicitly selected audio device causes reconnect loop due to stats showing no receive packets for the audio track.

Screenshots
If applicable, add screenshots to help explain the problem.

Platform

• OS: macOS
• Browser: Chrome
• Browser Version: Chrome Version 79.0.3945.88 (Official Build) (64-bit)
• Amazon Chime SDK GitHub Commit: 64e4da7

Allow for subscribing to beginning and end of attendee and volume updates.

Important: Please attach INFO-level logs with timestamps to the report from before the session started up until the point at which the unexpected behavior occured. For multi-participant calls, attach a log file for each participant if possible.

Chrome demo crash logs.txt

Meeting and attendee IDs:
List the meeting and attendee IDs that the attached logs apply to.

• Meeting ID: 4e4e6504-4d0e-401a-b524-7b1cedce8bd3
• Attendee ID: 3da4c6c3-3c97-4bd8-93f6-69fc08dabeef

Timeline
Outline the main actions the user performed and when:

2020-02-20T18:23:20.536Z [ERROR] SDK - realtime error: TypeError: Cannot read property 'style' of null: TypeError: Cannot read property 'style' of null
2020-02-20T18:23:20.537Z [ERROR] SDK - connection failed with status code: RealtimeApiFailed

Describe the bug
Describe the bug and the timestamp at which it happened relative to the timestamp in the log file.

A demo app's bug causes Chime SDK to stop the session because SDK does not catch an error in its real-time callback.

Steps to reproduce

1. Attendee A joins a meeting and does not mute audio.
2. Attendee B joins the same meeting and does not mute audio.
3. Attendee A clicks the screen viewing button.
4. After a few seconds, in the Attendee B browser's roster, Attendee A is removed from the meeting.
5. In the Attendee A's browser, Attendee A cannot hear any audio or click control buttons at the top.

Screenshots
If applicable, add screenshots to help explain the problem.

Platform

• OS: macOS Mojave
• Browser: Chrome
• Browser Version: 79.0
• Amazon Chime SDK GitHub Commit: 9720363

Describe the bug
It has been reported that the video tile update for an attendee can occur before the realtime controller reports that the attendee is present. We should look into why this can happen and see if there is an opportunity to strictly sequence these either within the SDK or on the server.

Screenshots
If applicable, add screenshots to help explain the problem.

Platform

• OS:
• Browser:
• Browser Version:
• Amazon Chime SDK GitHub Commit:

On a fresh Amazon Linux EC2 instance:

[ec2-user@ip-10-0-101-221 ~]$ git clone https://github.com/aws/amazon-chime-sdk-js.git
Cloning into 'amazon-chime-sdk-js'...
remote: Enumerating objects: 262, done.
remote: Counting objects: 100% (262/262), done.
remote: Compressing objects: 100% (190/190), done.
remote: Total 1685 (delta 69), reused 200 (delta 51), pack-reused 1423
Receiving objects: 100% (1685/1685), 838.40 KiB | 1.88 MiB/s, done.
Resolving deltas: 100% (708/708), done.

[ec2-user@ip-10-0-101-221 ~]$ cd amazon-chime-sdk-js/

[ec2-user@ip-10-0-101-221 amazon-chime-sdk-js]$ node -v
v13.3.0

[ec2-user@ip-10-0-101-221 amazon-chime-sdk-js]$ npm -v
6.13.1

[ec2-user@ip-10-0-101-221 amazon-chime-sdk-js]$ npm install amazon-chime-sdk-js --save
npm ERR! code ENOSELF
npm ERR! Refusing to install package with name "amazon-chime-sdk-js" under a package
npm ERR! also called "amazon-chime-sdk-js". Did you name your project the same
npm ERR! as the dependency you're installing?
npm ERR!
npm ERR! For more information, see:
npm ERR!     <https://docs.npmjs.com/cli/install#limitations-of-npms-install-algorithm>

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/ec2-user/.npm/_logs/2019-12-05T05_44_16_302Z-debug.log

From #198

From #198

What are you trying to do?

My assumption: This library is likely to be used by a team investing 1-4 person-months on an implementation. Ideally 2-3 person-weeks interacting with this specific sdk, and should be able to grasp the concepts and outline of the sdk in 1-2 days to begin an implementation.

I don't see there being proper documentation that is meant for a customer to complete this task in a reasonable amount of time.

I'm 15 hours into trying to use this library to have a 3 way video call. The documentation does not describe the concepts and flows I need. There is very little high level overview of the various components, and reading the source code takes too much dot connecting between too many files. I still don't know the basics of what I am supposed to do, I'm just connecting random things together to see if they work. There are hundreds of methods and properties to sort through and guess if they are needed for my use case.

How can the documentation be improved to help your use case?

1. The demos have three major flaws.
   1.1. They mix DOM manipulation code all over the place. This does not help show how the sdk is meant to be used.
   1.2. They add complexity without helping to demonstrate functionality. There are react components for a Button or Video tile that are not needed. Extra functions, abstractions, or embellishments are created which are not needed. This takes away from understanding the functionality the library provides. I shouldn't need to read the demos and constantly question "why is this needed" or "where exactly is the interaction with the sdk".
   1.3. I can't find a single line of documentation in the demos. Just a wall of 1200 lines in one example, or endless file jumping around.
2. High level concepts need to be explained. What is a tile, what is a local tile, what are the basic observable events I need to think about, what does the sdk manage for me, and what do I need to manage myself?
3. The code is not documented. For some reason if a tile is a local tile gets transform rotated by 180 degrees??? The docs themselves provide no more help, I would guess they have not been reviewed from a customer perspective. They seem designed for the development team, and are not customer-first.
4. I tried turning on the logger to help understand what is happening. There is far too much noise for me to understand how the library is intended to work.
5. There is a guide that basically stops at the point of adding audio onto the DOM, and trails off at the end by saying the customer now needs to hook up the video and all the observables? But far too little information is provided at that point for a user to understand exactly what needs to be hooked up.
6. Maybe I didn't understand, but the minimal demo isn't actually a demo, its just an html shell?

What documentation have you looked at so far?

I have tried reading the source code. I have read all the demos. I've tried deconstructing the demos, i've followed the guides, i've looked at all the documentation methods, I've tried drawing a map of the components by hand. The only decent documentation are some tests.

Important: Please attach INFO-level logs with timestamps to the report from before the session started up until the point at which the unexpected behavior occured. For multi-participant calls, attach a log file for each participant if possible.

Logs:
456e2208-1d52-4345-90b4-20c641d3543e-2019-11-21T20_18_18.674Z.log

Meeting and attendee IDs:
Meeting ID: 3203d66c-9c40-40bf-be55-727f638cf9b9
Attendee ID: 2479508e-70b0-4296-bd47-9b76e5d21ab7

Timeline

Describe the bug
This was a one-off issue described by the user as:

If party A is sharing screen, then party B wants to share screen and clicks start sharing (and A hasn't stopped sharing, so in effect swapping over) then it hangs

Screenshots
If applicable, add screenshots to help explain the problem.

Platform

• OS: Windows 10
• Browser: Chrome
• Browser Version: 78
• Amazon Chime SDK GitHub Commit: 7e6888f

From #198

Defined in SignalingProtocol.proto L114, BitrateFrame contains the information of average bitrate of video streams available, we should use this information during re-subscription.

What are you trying to do?

I'm trying to add and remove observers.

How can the documentation be improved to help your use case?

On the audio video facade the methods are addObserver/removeObserver. On the screen share facades they are registerObserver/unregisterObserver. These should be consistent.

Problem

From DefaultVideoTile.disconnectVideoStreamFromVideoElement():

// Need to yield the message loop before clearing `srcObject` to
// prevent Safari from crashing.
new AsyncScheduler().start(() => {
  videoElement.srcObject = null;
});

DefaultVideoTile.disconnectVideoStreamFromVideoElement() is setting videoElement.srcObject to null after a slight delay. However, disconnectVideoStreamFromVideoElement() and all callers, such as VideoTileController.unbindVideoElement()-are not async functions.

See this example:

// Assume that a <video> element "element" is bound to oldTileId.
// Unbind "element" asynchronously.
VideoTileController.unbindVideoElement(oldTileId);

// Bind "element" synchronously.
VideoTileController.bindVideoElement(newTileId, element);

// After binding "element," "element.srcObject" is set to null.

Solution

Option 1 (preferred):

Set videoElement.srcObject to null synchronously. We need to investigate why this can cause Safari to crash.

Option 2:

Make all callers to async. This requires significant changes that should be related to 2.0.0.

Describe the bug
After backgrounding Safari, the microphone audio stops sending to other participants on the call. To background Safari, the window either needs to be minimized to the dock or the user needs to switch to another desktop on macOS. Simply bringing another window to the foreground is not sufficient to trigger this issue.

Platform

• OS: macOS Mojave 10.14.6
• Browser: Safari
• Browser Version: 13.0.4 (14608.4.9.1.4)
• Amazon Chime SDK GitHub Commit: 64a5787

INFO log
[INFO] Express::MeetingSaga::startScreenShare: Screen share is not supported for browser or version | web.aa1a246dfe507dcb85f3.js:1:1163475

Discribe the bug
Hi, the documentation (amazon-chime-user-guide/doc_source/screen-share.md) states that the web application supports screen share on Firefox for Linux OS without the need of plugins. However it seems that it is not supported for Firefox ver 74.0 (64bit) for Ubuntu, screen share is unable to start.

If there are no plans to support it, should the documentation change?

Screenshots

Platform

• OS: Ubuntu 16.04.6 LTS 64-bit
• Browser: Firefox
• Browser Version: 74.0 (64bit) for Ubuntu.
• Amazon Chime SDK GitHub Commit: N/A

What are you trying to do?

Join users on different machines to the local server.

How can the documentation be improved to help your use case?

Add a "limitations of the local app" section to README to explain that meetings created by different local servers are different meetings even if they use the same meeting name.

What documentation have you looked at so far?

README.md

Amazon Chime SDK Integration with Ionic Framework

Platform

• OS: Android Version 9

Bug Description

We are trying to integrate the Amazon Chime SDK with Ionic framework(using Angular) in Android device. We were able to join a meeting from browser and ionic integrated android device, And able to share audio/video from browser application to android device.We are getting video/audio preview in device shared by browser application.

But, the issue is we are unable to access the device's inbuilt audio/video hardware components permission and hence we are not getting the preview in desktop.

We even tried to access the device's audio/video components by writing the following lines in AndroidManifest.xml and have given app-level permissions in device to access Camera and Microphone.

<uses-permission android:name="android.permission.CAMERA" />
<uses-permission android:name="android.permission.RECORD_AUDIO" />

When we try to toggle camera/microphone we are getting an error in console and same is attached below.

We would like to know that, is Amazon Chime SDK supports to integrate with Mobile applications?
If yes please let us know how we can solve the below issue.

Screenshots

What are you trying to do?

There have been several issues filed such as #198 on the lack of sufficient documentation for basic scenarios on the JS SDK such as video join, basic audio controls and notifications. This is tracking improvement and discoverability in that front. Also point to code snippets in a demo to support the learning

How can the documentation be improved to help your use case?

Improve the GettingStarted or ReadMe documentation

What documentation have you looked at so far?

README.md, Amazon Chime SDK Developer Guide, GettingStarted

Reproduces in the demo app. On macOS Chrome:

1. In browser window 1, join A and enable video
2. In browser window 2, join B and enable video
3. Confirm both windows show local/remote videos
4. In browser window 1, open a new tab (e.g. example.com) and leave focused
5. In browser window 2, toggle B video off and on
6. Switch back to tab in browser window 1 with participant A
7. Video is empty

From #198

Describe the bug
Add unit tests for the following classes:

ScreenShareViewFacade - (

amazon-chime-sdk-js/test/screenshareviewfacade/DefaultScreenShareViewFacade.test.ts

Line 5 in dd65d7f

// TODO: tests and remove exclude in package.json

)
ScreenShareFacade - (

amazon-chime-sdk-js/test/screensharefacade/DefaultScreenShareFacade.test.ts

Line 5 in dd65d7f

// TODO: tests and remove exclude in package.json

)
DefaultDeviceController

Screenshots

Platform

• OS:
• Browser:
• Browser Version:
• Amazon Chime SDK GitHub Commit:

Important: Please attach INFO-level logs with timestamps to the report from before the session started up until the point at which the unexpected behavior occured. For multi-participant calls, attach a log file for each participant if possible.

Meeting and attendee IDs:
List the meeting and attendee IDs that the attached logs apply to.

Timeline
Outline the main actions the user performed and when:

Describe the bug
This is more of a feature request.

Currently, we can only get the muted state of a remove participant by passing in a callback function into realtimeSubscribeToVolumeIndicator.

It'd be good if the remote muted/unmuted stated was handled separately, considering the audio streams are all being consolidated into 1 audio stream, there are use cases where the consuming app would not have a need to subscribe to individual volume events.

Screenshots
If applicable, add screenshots to help explain the problem.

Platform

• OS:
• Browser:
• Browser Version:
• Amazon Chime SDK GitHub Commit:

Where necessary business logic should also be lightly commented when its purpose is not clear.

From #198

Describe the bug
When in Safari, the browser tab will crash and reload the page when remote video tiles are added or toggled.

There are two different crash signatures for Safari that can be seen in the system logs:

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   com.apple.WebCore                 0x0000000102fab33c WebCore::MediaPlayerPrivateMediaStreamAVFObjC::sampleBufferUpdated(WebCore::MediaStreamTrackPrivate&, WebCore::MediaSample&) + 28
1   com.apple.WebCore                 0x000000010457036c WebCore::MediaStreamTrackPrivate::forEachObserver(WTF::Function<void (WebCore::MediaStreamTrackPrivate::Observer&)> const&) const + 652
2   com.apple.WebCore                 0x0000000104570b43 WebCore::MediaStreamTrackPrivate::videoSampleAvailable(WebCore::MediaSample&) + 259
3   com.apple.WebCore                 0x0000000104574d4c WebCore::RealtimeMediaSource::forEachObserver(WTF::Function<void (WebCore::RealtimeMediaSource::Observer&)> const&) const + 652
4   com.apple.WebCore                 0x0000000104575068 WebCore::RealtimeMediaSource::videoSampleAvailable(WebCore::MediaSample&) + 280
5   com.apple.WebCore                 0x000000010336a7a9 WTF::Detail::CallableWrapper<WebCore::RealtimeIncomingVideoSourceCocoa::OnFrame(webrtc::VideoFrame const&)::$_7, void>::call() + 265
6   com.apple.JavaScriptCore          0x00000004208f65f9 WTF::dispatchFunctionsFromMainThread() + 361
7   com.apple.Foundation              0x00007fff4e41b302 __NSThreadPerformPerform + 328
8   com.apple.CoreFoundation          0x00007fff4c13fde3 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 17
9   com.apple.CoreFoundation          0x00007fff4c13fd89 __CFRunLoopDoSource0 + 108
10  com.apple.CoreFoundation          0x00007fff4c12374b __CFRunLoopDoSources0 + 195
11  com.apple.CoreFoundation          0x00007fff4c122d15 __CFRunLoopRun + 1189
12  com.apple.CoreFoundation          0x00007fff4c12261e CFRunLoopRunSpecific + 455
13  com.apple.Foundation              0x00007fff4e38732f -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 280
14  com.apple.Foundation              0x00007fff4e387204 -[NSRunLoop(NSRunLoop) run] + 76
15  libxpc.dylib                      0x00007fff782b6077 _xpc_objc_main + 552
16  libxpc.dylib                      0x00007fff782b5b79 xpc_main + 433
17  com.apple.WebKit                  0x0000000101ea0e53 WebKit::XPCServiceMain(int, char const**) + 547
18  libdyld.dylib                     0x00007fff7807d3d5 start + 1

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   com.apple.WebCore                 0x000000010b85873b WTF::Detail::CallableWrapper<WebCore::MediaStreamTrackPrivate::sourceMutedChanged()::$_18, void, WebCore::MediaStreamTrackPrivate::Observer&>::call(WebCore::MediaStreamTrackPrivate::Observer&) + 11
1   com.apple.WebCore                 0x000000010b85536c WebCore::MediaStreamTrackPrivate::forEachObserver(WTF::Function<void (WebCore::MediaStreamTrackPrivate::Observer&)> const&) const + 652
2   com.apple.WebCore                 0x000000010b8559c9 WebCore::MediaStreamTrackPrivate::sourceMutedChanged() + 57
3   com.apple.WebCore                 0x000000010b859d4c WebCore::RealtimeMediaSource::forEachObserver(WTF::Function<void (WebCore::RealtimeMediaSource::Observer&)> const&) const + 652
4   com.apple.WebCore                 0x000000010b859a4b WebCore::RealtimeMediaSource::notifyMutedChange(bool) + 155
5   com.apple.WebCore                 0x000000010b8564c0 WebCore::RealtimeIncomingVideoSource::setSourceTrack(rtc::scoped_refptr<webrtc::VideoTrackInterface>&&) + 112
6   com.apple.WebCore                 0x000000010a235c08 WTF::Detail::CallableWrapper<WebCore::LibWebRTCMediaEndpoint::OnTrack(rtc::scoped_refptr<webrtc::RtpTransceiverInterface>)::$_13, void>::call() + 600
7   com.apple.JavaScriptCore          0x000000010d7585f9 WTF::dispatchFunctionsFromMainThread() + 361
8   com.apple.Foundation              0x00007fff4fe3a302 __NSThreadPerformPerform + 328
9   com.apple.CoreFoundation          0x00007fff4db5ede3 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 17
10  com.apple.CoreFoundation          0x00007fff4db5ed89 __CFRunLoopDoSource0 + 108
11  com.apple.CoreFoundation          0x00007fff4db4274b __CFRunLoopDoSources0 + 195
12  com.apple.CoreFoundation          0x00007fff4db41d15 __CFRunLoopRun + 1189
13  com.apple.CoreFoundation          0x00007fff4db4161e CFRunLoopRunSpecific + 455
14  com.apple.Foundation              0x00007fff4fda632f -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 280
15  com.apple.Foundation              0x00007fff4fda6204 -[NSRunLoop(NSRunLoop) run] + 76
16  libxpc.dylib                      0x00007fff79cd5077 _xpc_objc_main + 552
17  libxpc.dylib                      0x00007fff79cd4b79 xpc_main + 433
18  com.apple.WebKit                  0x0000000109183e53 WebKit::XPCServiceMain(int, char const**) + 547
19  libdyld.dylib                     0x00007fff79a9c3d5 start + 1

Platform

• OS: macOS
• Browser: Safari
• Browser Version: 13.0.3 (14608.3.10.10.1)
• Amazon Chime SDK GitHub Commit: dd65d7f

The master branch contains a demo example named demos/browser/app/meetingV2. In there the class DefaultModality is used. This class does not exist in v1.1.0 of the SDK. When trying to install the latest version of the SDK via yarn upgrade the following is output:

∴ yarn upgrade chime
yarn upgrade v1.22.0
Couldn't find any versions for "amazon-chime-sdk-js" that matches "^1.1.22"
? Please choose a version of "amazon-chime-sdk-js" from this list: (Use arrow keys)
❯ 1.1.0
  1.0.0

When will the latest version from master be available to install via yarn?

Describe the bug
We run into the following circular dependency warnings when running ng serve with the Angular CLI.:

WARNING in Circular dependency detected:
../chime-sdk/chime-src/dist/src/maybe/Maybe.js -> ../chime-sdk/chime-src/dist/src/maybe/None.js -> ../chime-sdk/chime-src/dist/src/maybe/Maybe.js

WARNING in Circular dependency detected:
../chime-sdk/chime-src/dist/src/maybe/None.js -> ../chime-sdk/chime-src/dist/src/maybe/Maybe.js -> ../chime-sdk/chime-src/dist/src/maybe/None.js

WARNING in Circular dependency detected:
../chime-sdk/chime-src/dist/src/maybe/Some.js -> ../chime-sdk/chime-src/dist/src/maybe/Maybe.js -> ../chime-sdk/chime-src/dist/src/maybe/Some.js

Platform
Node: v10.15.3
Project: TypeScript, but specifically within Angular
Bundler: Angular CLI internally uses webpack IIRC

Send/receive bandwidth metrics for Safari not plumbed through observer callback

From #198

What are you trying to do?

I would like to provide my users the ability to record their meeting and store in S3 for later viewing.

How can the documentation be improved to help your use case?

Perhaps provide a roadmap, or a way to request enhancements?

What documentation have you looked at so far?

All of it. :)

Describe the bug
Issue was reproduced on browser sample application be following these steps.

User A and B are joined to a meeting session

User A starts screen share view
User B starts screen sharing and share an application
User A can see the screen share
Now User B closes the application
User A can still see the screen share

Screenshots
If applicable, add screenshots to help explain the problem.

Platform

• OS: Windows 10
• Browser: Firefox
• Browser Version: 71.0 (64-bit)
• Amazon Chime SDK GitHub Commit:

From #198

Logs
logs_android_tablet_test.txt

Describe the bug
Describe the bug and the timestamp at which it happened relative to the timestamp in the log file.
I am testing by running the android demo on two android devices: Samsung Tab A and Pixel 3.
Both devices can join the same meeting and see the other device's video feed.
Neither device outputs any audio despite being on full volume, unmuted, and mics on.
I'm wondering how to get audio working and if it's been working at all since the demo was created.

Platform

• OS: Android v9
• Browser: Chromium
• Amazon Chime SDK GitHub Commit: Add Android web view demo 3952080 Kyu Simm [email protected] Dec 23, 2019 at 2:59 PM