singulli1

I will: While I'm doing this, can you answer the following: **From AWS documentation:** https://docs.aws.amazon.com/chime-sdk/latest/dg/websockets.html When the application uses a close code to reconnect, the application should: 1. Call the...

We updated amazon-chime-sdk-js to 3.6.0 We have 25 users chatting heavily in NM. Things now see to work for a while, then fall apart. I'm attaching an example log file:...

This is great news. How long (best guess) until this is available in a release? We are trying to decide if we should revert back to 2.30.1 or wait for...

We applied the fix, we are not getting tons of error messages intermittently See attached log file. This is a huge deal for us. [chatLog4.txt](https://github.com/aws/amazon-chime-sdk-js/files/9417704/chatLog4.txt)

{ "sequenceNumber": 0, "message": "adding messaging observer", "timestampMs": 1661348491672, "logLevel": "INFO", "tenantID": "27", "sessionId": "c4c6041f-da73-4d5e-a45d-d88037b8ebae", "userName": "MSnookFehr" } { "sequenceNumber": 1, "message": "opening connection to wss://node001.ue1.ws-messaging.chime.aws/connect?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=ASIA23LK62QLMEZNOYUB%2F20220824%2Fus-east-1%2Fchime%2Faws4_request&X-Amz-Date=20220824T134131Z&X-Amz-Expires=10&X-Amz-Security-Token=FwoGZXIvYXdzED8aDCJvwZdV3PA%2B%2FKi56iKVApqRTqNovIv4wRar2BAmOpUY5uB0Om6y9TqDnFJIS7IRLA6SM2KrKKJfdFRUtYZONO%2B20dfp6joVqKSDQX5hUJYZmRv3TjHorYh3BJ5k3ZWAaA5CuFkSgB1uxgrx2zuDboZuUYV8e3ZA53OduVPbYmrpTy7hzGDo7j67f%2F75LGdwUk%2BDckfRQP4N4V%2BUU6ON0JyoV8vhcy%2FxV8hh0iK9K5twOfS4%2FoAKUmBHyuDQnISqwpz%2BJuYISCP0zMShh5JJ2tFduWFuKFxt%2BfZ7zKGNyJ8HGaz2Y7jeWClBQCUxT4pCCHwidsdRMYTNNEJxAXntmUxTmg%2BRRESOWegga1CvWSRsisXX7FKfaIU3QiKMcLe3CadU6Tkog9WYmAYyLe%2BMAQ4R0uImKQX1x4apMuze44atZ%2FVw2vE%2FtrP3qbHe%2FuLomzTi6VhACBoHRA%3D%3D&X-Amz-SignedHeaders=host&X-Amzn-User-Agent=chrome-104&X-Amzn-Version=3.7.0&sessionId=c4c6041f-da73-4d5e-a45d-d88037b8ebae&userArn=arn%3Aaws%3Achime%3Aus-east-1%3A745938015254%3Aapp-instance%2F1aefb1f1-34c1-44dc-9b91-9981f848e5b9%2Fuser%2F27-5492-21f34b2f-0fe0-4baa-8a1a-cabe570923c5&X-Amz-Signature=6e0a74f401dba141c0df7aceae6ded37acfc020a6a54ec66843a215464b2e320", "timestampMs": 1661348491762, "logLevel": "INFO",...

**Message Session Connection:** async connect(currentUser: User, currentTenant: Tenant) { this.initialize(); console.log(`Starting Chat Session`); this.currentUser = currentUser; this.currentTenant = currentTenant; // loggers start this.consoleLogger = new ConsoleLogger('SDK Chat', LogLevel.INFO); const url...

**imports** import { v4 as uuid } from 'uuid'; import AWS from 'aws-sdk'; import { ChimeAPIService } from './chimeAPI.service'; import { Injectable, Output, EventEmitter } from '@angular/core'; import { chimeChatConfigPsykdesk,...

If we revert to 2.31.0 will we have the same issue?

package.json: "aws-sdk": "^2.1148.0", npm list aws-sdk C:\Users\scott\projectsAngular\psykdesk-mark7>npm list aws-sdk [email protected] C:\Users\scott\projectsAngular\psykdesk-mark7 `-- [email protected]

These logs are coming from the server in our production environment - and they are sporadic, not everyone is having the issue. So the question is how to recreate to...