'/participant/connection' were called twice with connect event

Question

'/participant/connection' were called twice with connect event

cythiaY opened this issue 2 years ago · 13 comments

Answer 1 · 2022-07-07T07:42:30.000Z

Verison：1.1.12
Usage：

 const customerChatSession = connect.ChatSession.create({
      chatDetails: {
        contactId: ****,
        participantId: ****,
        participantToken: ****,
      },
      options: {
        region: "us-west-2",
      },
      type: connect.ChatSession.SessionTypes.CUSTOMER,
    });

    await customerChatSession.connect();

Network 👇:

Other，I can't pass “Type” parameter to function connect like CreateParticipantConnection

Answer 2 · 2022-07-07T07:53:35.000Z

This should be two separate calls to the participant service. The first one is an OPTIONS method, the second the actual POST call.

Answer 3 · 2022-07-07T08:04:47.000Z

Noop, both are POST method. And return different response.
first:

second:

Answer 4 · 2022-07-11T12:26:21.000Z

Can anyone help me？😣

Answer 5 · 2022-07-11T22:42:45.000Z

Hi, I have a few questions

do you know if this is a new issue in the latest version or was it existing in old versions as well?
can you check in browser how many websocket connections were established?
Please let me know. Thanks

Answer 6 · 2022-07-15T08:17:41.000Z

This behavior is ongoing for some time. Possibly since the beginning of the library. There was a release awhile back that was designed to eliminate the double calls, but it was rolled back in the next release because of some issues that I do not have details on. The release that addressed this was https://github.com/amazon-connect/amazon-connect-chatjs/tree/1.0.7, then it was rolled back.

Answer 7 · 2022-07-19T11:23:24.000Z

This behavior is ongoing for some time. Possibly since the beginning of the library. There was a release awhile back that was designed to eliminate the double calls, but it was rolled back in the next release because of some issues that I do not have details on. The release that addressed this was https://github.com/amazon-connect/amazon-connect-chatjs/tree/1.0.7, then it was rolled back.

Verison 1.0.7 doesn't work, even without TS.
When will u fix this problem in the future? 😊

Answer 8 · 2022-07-19T20:59:06.000Z

We have the item to fix it in our backlog but it hasn't been prioritized yet. Can you explain more on how this behavior becomes a problem for you?

Answer 9 · 2022-07-20T07:06:08.000Z

It's not urgent now.
We just listen to the ’connect‘ event in server to do something. We have found another workaround.

Answer 10 · 2022-08-29T15:02:13.000Z

I am see the same behaviour, the connection is called twice, each time it turn a different websocket url(token is different), the library use the 2nd response token to establish the websocket.

Answer 11 · 2022-09-16T14:32:23.000Z

I believe the problem probably related to the connectionDetailsProvider.js

baseConnectionHelper.js (line 32) ---> invokes this.connectionDetailsProvider.fetchConnectionToken()
LpcConnectionHelper.js (line 139) ----> invokes the connectionDetailsProvider.fetchConnectionDetails()

these calls will cause the provide to _callCreateParticipantConnection twice (and create two participant connections).

the fetchConnectionDetails() and fetchConnectionToken() should check if connectionDetails or token already available, if not make a connection otherwise return it.

Answer 12 · 2023-02-20T03:40:40.000Z

This may be related to #31.

Answer 13 · 2023-02-21T20:36:39.000Z

This issue is fixed in the latest release 1.3.2